Closed yevhenii-nadtochii closed 1 year ago
Merging #69 (2cd0001) into master (3a2ba61) will not change coverage. The diff coverage is
n/a
.
@armiol @alexander-yevsyukov PTAL
And let's discuss next steps after review of this PR.
@armiol @alexander-yevsyukov PTAL
This PR updates README files.
The following modules have been updated:
tests/logging-smoke-test
logging-fake-backend
logging-context
logging-backend
logging
flogger
I've renamed
Module.md
toREADME.md
becauseREADME
files are rendered by GitHub even if they are in nested directories.Possible actions:
slf4j
backend, and after repackaging we are incompatible with Flogger's one. We should either create an issue to add this backend or remove two test modules that use this backend.io.spine.testing.logging
package intests/fixtures
module. And we also haveio.spine.logging.testing
intestutil-logging
. Earlier, we decided to go with the latter option.logging-fake-backend
tobackends/jvm-dynamic-backend
. We don't need "logging" prefix because this module is not published. Also, I'm not sure whether to extractcaptureLogData()
to a separate module. It feels so, but I haven't come up with a module name.SimpleLoggerBackend
. We have our own default backend (StdLoggerBackend
), so Flogger's one can be removed.logging
prefix in module names? We use it for published modules, and it starts to pollute modules hierarchy with long names. MaybespinePublihsing{}
can do it for us.Flogger
(#62). Putting ofspine-logging
on the classpath doesn't lead to the console output anymore. It leads to an error. We also have to putlogging-backend
explicitly.