-
|
Is there a timeframe when it's expected that @loopback/logging will no longer be in "Experimental" state? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @cuttingd, there's no timeline on bringing This is partly due to the lack of discussion surrounding the package's design. Hence, there is a higher chance that we may expand the package's capabilities beyond what was initially conceived. However, it should be fine to use it in production as:
Hence we do not foresee any major changes to this package for the foreseeable future. As long as the NPM-default caret SemVer range is used (e.g. "^0.1.0"), no breaking changes would be installed. As a general principle LoopBack 4 is maintained with a less rapid development cycle. That is, LoopBack 4 maintainers do not make sweeping breaking changes nor do we remove existing functionality without good reason. Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you |
Beta Was this translation helpful? Give feedback.
Hi @cuttingd, there's no timeline on bringing
@loopback/loggingto v1 / non-experimental.This is partly due to the lack of discussion surrounding the package's design. Hence, there is a higher chance that we may expand the package's capabilities beyond what was initially conceived.
However, it should be fine to use it in production as:
Hence we do not foresee any major changes to this package for the fores…