Pelias is a geocoder powered completely by open data, available freely to everyone.
Local Installation · Cloud Webservice · Documentation · Community Chat
What is Pelias?
Pelias is a search engine for places worldwide, powered by open data. It turns addresses and place names into geographic coordinates, and turns geographic coordinates into places and addresses. With Pelias, you're able to turn your users' place searches into actionable geodata and transform your geodata into real places.
We think open data, open source, and open strategy win over proprietary solutions at any part of the stack and we want to ensure the services we offer are in line with that vision. We believe that an open geocoder improves over the long-term only if the community can incorporate truly representative local knowledge.
This module is used for testing logging events in Pelias projects. proxyquire is the supported module for overriding dependencies in which this module is used.
$ npm install pelias-mock-logger --save-devThe pelias-mock-logger npm module can be found here:
https://npmjs.org/package/pelias-mock-logger
Traditionally, testing logging events required quite a bit of setup with proxyquire:
const errorMessages = [];
var service = proxyquire('../../../service/interpolation', {
'pelias-logger': {
get: () => {
return {
error: (msg) => { errorMessages.push(msg); },
info: (msg) => {}
};
}
}
}).search();
t.deepEquals(errorMessages, ['RequireTransport: failed to connect to interpolation service']);Using the pelias-mock-logger module, this code can be shortened to:
const logger = require('pelias-mock-logger')();
var adapter = proxyquire('../../../service/interpolation', {
'pelias-logger': logger
}).search();
t.deepEquals(logger.getErrorMessages(), ['RequireTransport: failed to connect to interpolation service']);- logging events
error(msg)warn(msg)info(msg)verbose(msg)debug(msg)silly(msg)
getLayer(): returns the value passed to.get()inrequire( 'pelias-logger' ).get( 'api' )getLevels(): returns the supported logging levels:error,warn,info,verbose,debug, andsillygetMessages(level, pattern): returns all messages logged at a level, optionally matching a pattern- Examples:
getMessages('error')getMessages('error', /backend error occurred/)
- Examples:
hasMessages(level, pattern): returns whether messages were logged at a level, optionally matching a pattern- Examples:
hasMessages('error')hasMessages('error', /backend error occurred/)
- Examples:
isMessage(level, pattern): returns whether the supplied pattern matches or is equal to any messages logged at the specified level- Examples
isMessage('error', /backend error occurred)isMessage('error', 'a backend error occurred, contact the Pelias team for assistance')
- Examples
- level-specific functions
- getMessages: returns all messages logged at the level specified in function name, optionally matching a pattern
getErrorMessages(pattern)getWarnMessages(pattern)getInfoMessages(pattern)getVerboseMessages(pattern)getDebugMessages(pattern)getSillyMessages(pattern)
- hasMessages: returns whether messages were logged at the level specified in function name, optionally matching a pattern
hasErrorMessages(pattern)hasWarnMessages(pattern)hasInfoMessages(pattern)hasVerboseMessages(pattern)hasDebugMessages(pattern)hasSillyMessages(pattern)
- isMessage: returns whether the supplied pattern matches or is equal to any messages logged at the level specified in the function name
isErrorMessages(pattern)isWarnMessages(pattern)isInfoMessages(pattern)isVerboseMessages(pattern)isDebugMessages(pattern)isSillyMessages(pattern)
- getMessages: returns all messages logged at the level specified in function name, optionally matching a pattern
Please fork and pull request against upstream master on a feature branch.
Provide unit tests in the test directory.
$ npm test
