refactor: make the Unity console a first-class log target - #43
Merged
Conversation
…e exit and reloads
…ean clickable entries
… on GC finalization
imurashka
force-pushed
the
imurashka/unify-target-pipeline
branch
from
July 5, 2026 20:26
3aeee68 to
1e2d6ed
Compare
imurashka
force-pushed
the
imurashka/unify-target-pipeline
branch
from
July 6, 2026 18:16
c4e6f3b to
2e8de06
Compare
…ck noise frame names
…regateException stack overflow
… reflection on load
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
1 participant
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.
Reworks the logging core so the Unity console is just another target: ULogger steals Debug's log handler and delivers every log and exception through one sync-or-async target pipeline, dropping the old logMessageReceived round-trip. In the editor, console entries now get a cleaned, clickable stack via managed-callback entries (double-click lands on the real call site), background-thread logs are marshaled to the main thread, and async/engine/threading noise frames are filtered out by extensible groups. All Unity-interop and stack handling is isolated under Internal/UnityInterop for easier per-platform maintenance.