fix(configuration): add log level support via env variables #370
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
- Introduced `SENTRY_LOG_LEVEL` handling in `ConfigurationValues` to allow dynamic log level configuration. - Updated the `merged` method to prioritize `platformEnv.logLevel` over other sources. - Enhanced tests to cover new log level functionality, including handling empty values and priority merging.
- Updated the `enumerateDebugSearchRoots` function to yield a single intermediates directory for release builds, removing specific paths to avoid checksum conflicts during uploads.
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.
📜 Description
Fixes log level not being set through env variable
💡 Motivation and Context
Fixes #366
💚 How did you test it?
Unit test
📝 Checklist
🔮 Next steps