Allow tags to point to a custom level defined in pino's customLevels

[aalimovs]

You can define customLevels with pino, e.g.

customLevels: {
  bar: 123
}

Meaning when logging with logger.bar('hello world') it results in { level: 123, ... }.

hapi-pino accepts an option of tags, which is a map of hapi log tags to pino's level. However, the library has a hardcoded list of pino levels:

const levels = ['trace', 'debug', 'info', 'warn', 'error']

It means you cannot define tags which would point to a custom level defined via customLevels:

options: {
    customLevels: {
        bar: 123
    },
    tags: {
        foo: 'bar',
    }
}

Above throws an error invalid tag levels because it checks level bar against ['trace', 'debug', 'info', 'warn', 'error'].

This PR compares bar against Object.keys(logger.levels.values), which is the valid array of levels that pino accepts, including those defined via customLevels.

PR also adds a missing fatal level to levelTags object, fixing server.log('fatal', 'bye world'); resulting in level: 30/info.

[mcollina]

lgtm

[coveralls]

Coverage increased (+0.01%) to 99.098% when pulling 9a5bc12 on aalimovs:master into fb70517 on pinojs:master.

[mcollina]

CI is failing

[aalimovs]

Hm it seems completely unrelated to the changes (happens pre-PR too). Something internally in hapi's lib/request.js changed starting from v19 where doing server.inject with simulate close true like:

server.inject({
  url: '/',
  method: 'POST',
  simulate: {
    close: true
  }
})

Throws an error at @hapi/hapi/lib/request.js:497:31

[mcollina]

Can you send another PR that fixes those? I'm not really using this module and I'm not making a release with red CI.

[aalimovs]

@mcollina this should be fixed now pulling in the merged #137

However, I'm not sure what's the deal now with the new pipelines.

Fails my end with unrelated Coveralls Parallel errors, https://github.com/aalimovs/hapi-pino/runs/3831798686?check_suite_focus=true

And it's waiting for approval here https://github.com/pinojs/hapi-pino/actions/runs/1317758243

[mcollina]

lgtm

[mcollina]

@lauraseidler can you take a look?

[lauraseidler]

LGTM - not sure what went wrong with the tests there in the beginning, but looks fine now?

[lauraseidler]

Ah I see - it's failing on your fork because that's a different repo and a different token.. not sure how to solve this rn, will take a look later. But as it's running fine on this repo, I guess it's okay for now.

[lauraseidler]

I published a new version 8.5.0 that includes these changes - thanks!