Fix YamlException.ToString() to include stack trace#1084
Merged
EdwardCooke merged 5 commits intoaaubry:masterfrom Apr 9, 2026
Merged
Fix YamlException.ToString() to include stack trace#1084EdwardCooke merged 5 commits intoaaubry:masterfrom
EdwardCooke merged 5 commits intoaaubry:masterfrom
Conversation
EdwardCooke
approved these changes
Apr 9, 2026
This was referenced Apr 9, 2026
This was referenced Apr 10, 2026
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
2 participants
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.
I’ve updated
YamlException.ToString()to includebase.ToString(). The previous version was overriding the standard .NET behavior and swallowing the stack trace and inner exceptions, which made debugging harder.This change restores the diagnostic report while keeping the YAML position markers at the start of the string. I also added a new
ToMessage()method for the keep the "Position - Message" format, which is clean for where you don't want to show a full stack trace.I've also updated the unit tests to match the new format and verified everything passes.
close #1080