-
Notifications
You must be signed in to change notification settings - Fork 0
Adding Log Propagate #503
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
Merged
Adding Log Propagate #503
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
- Added the log_propagate parameter to the config_log function, allowing users to control whether log messages propagate to ancestor loggers. - Updated the module and function docstrings to document the new log_propagate option and its default value (False). - Modified the logging configuration logic to set the propagate attribute on all managed loggers according to the log_propagate argument, helping prevent duplicate log lines when intercepting standard logging. - Updated usage examples in the documentation to include log_propagate. - Ensured all unit tests and test calls to config_log explicitly pass the log_propagate argument for clarity and coverage. - This change improves flexibility and prevents duplicate log entries when integrating loguru with standard Python logging.
…pt execution from module and coverage; note that the same example usage code is available in examples/validate_email.py
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
enhancement
New feature or request
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.
Pull Request Description: Adding Log Propagate
Motivation
This pull request introduces the Log Propagate feature to our project, which enhances our logging capabilities. By integrating log propagation, we ensure that log messages are consistently passed through different layers of our application. This improvement is crucial for debugging and tracking the flow of execution across various modules, thereby increasing the maintainability and observability of our codebase.
Changes Made
Updated Devcontainer Configuration:
Docker Compose Configuration:
Changelog Updates:
Coverage Badge Update:
Code Adjustments:
Benefits
This change is a step towards a more robust architecture, ultimately leading to a more reliable and maintainable codebase.