Skip to content

Conversation

@joshystuart
Copy link
Collaborator

Since @rafterjs/logger is included by default in @rajfterjs/api it would never be properly overridden by loggers either passed into Server or as new logger plugins.

I think there's more that can be done about reusing the logger that was passed into rafter instead of autoloading it. I think that will mean ignoring autoloaded loggers and just reusing the passed one. I think we should also allow passing in of a loggerFactory into Server since many rafter services now switched over to using a loggerFactory instead of a logger. Might need to explore this further.

I also split out the json renderer so it can be reused in other contexts as it's own dependency

Im not sure if this is the right approach.
I think there's something that can be dont about reusing the logger that was passed into rafter instead of autoloading it.
I also split out the json renderer so it can be reused in other contexts as it's own dependency

TODO
* add a logger check in the autoloader.
* allow passing in of a loggerFactory too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants