✨ Allow custom log levels #683
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Problem: - Many logging backends have varying ideas of what a log level is. The MIPI-SysT spec defines two user-defined values. It would be nice to use a strongly-typed enumeration in application code that can re-spell the `USER1` and `USER2` values. Solution: - Make logging level-agnostic. - The MIPI-SysT levels are provided for default use, but they aren't required.
elbeno
force-pushed
the
custom-log-level
branch
from
9f7e493 to
4dbdb14
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem:
spec defines two user-defined values. It would be nice to use a strongly-typed
enumeration in application code that can re-spell the
USER1andUSER2values.
Solution: