Repository navigation
fix: MultiStream always targets console and file logger - #8
Merged
Merged
Conversation
CONSOLIX_LOG_STREAM now always writes to console (index 0) and file logger (index 3), plus any extra backends from m_logger_indices. Previously broadcast (-1) skipped single-mode backends (console), and non-empty m_logger_indices skipped console/file.
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
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.
Ensures CONSOLIX_LOG_STREAM always writes to the console backend and file logger, plus any extra backends specified via CONSOLIX_LOG_STREAM_EX. Previously the broadcast (-1) approach skipped single-mode backends, and non-empty m_logger_indices skipped the default console/file targets.