feature: logger hook functions

[idbenami]

added the ability to add hooks functions per each log level or all of them.
hooks are passed in the options param in the module root functions.

example:

ContextLoggerModule.forRoot({
  hooks: {
    error: [(message, bindings) => {
      generalErrorsCounter.add(1, bindings);
    }]
  }
})

[Copilot]

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

[AdirD]

not sure I understand the purpose behind this, you want to be able to shove side effects right before the log is sent? But the hooks are set one time during app bootstrap, why not use the context interceptor to enrich the context and such new fields enrichment will be done automatically?

[idbenami]

This isn’t meant for enriching the logs themselves, but rather for triggering small side effects right before or after a log is sent (could be changed) - like tracking metrics or triggering alerts.

It’s meant as a lightweight runtime hook without needing to run the same block of code before/after each log, wrap logger functions or modify individual log calls.

[AdirD]

as in "also send a sentry when an error is logged?"

[idbenami]

yeah, for example..

[github-actions]

🎉 This PR is included in version 1.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀