Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Establishing a filtering mechanism to optionally vend loggers #72

Merged
merged 4 commits into from
May 3, 2024

Conversation

heckj
Copy link
Collaborator

@heckj heckj commented May 2, 2024

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

@heckj heckj self-assigned this May 2, 2024
@heckj heckj merged commit 99a8448 into main May 3, 2024
1 check passed
@heckj heckj deleted the filteredLogging branch May 3, 2024 16:54
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.

Logging is useful when you need it, but an annoying flood otherwise
1 participant