Establishing a filtering mechanism to optionally vend loggers #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #66
I'm annoyed with this as a pattern, but I couldn't seem to come up with a way to wrap OSLog due to compiler-magic that enables the privacy interpolation, and I thought it was more valuable to keep that privacy capability in place. So instead Ive wrapped all calls to .trace() or .debug() in checks against a dynamic log verbosity (at least for the repo) so that relevant information won't be spewing out into the Unified Logging system on Apple platforms.
Apple's tools are substandard to keep the unified logging information from being overwhelming while doing general debugging, but it is handy when you need it, so I took the time to make it dynamic and programmaticly controllable