feat(scripting): add severity-aware Problems panel - #246
Merged
Conversation
Lists every parse-fidelity diagnostic for the selected clip in a bottom-docked panel instead of the status bar's aggregate-only summary, with an inline XML snippet at the diagnostic's location. - Add ClipParseLocationResolver to resolve a diagnostic's XPath-style location back to XML for the panel's detail pane. - Add ClipParseReport.HighestSeverity and wire severity-aware glyphs/colors into the panel rows, the clip-tree badge, and the status bar summary (previously a flat orange "!" regardless of severity). - Sort panel rows worst-severity-first and show a per-severity count breakdown in the header instead of a flat total.
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.
Summary
Ctrl+Shift+M, or click the status-bar summary) listing every diagnostic for the selected clip, with an inline XML snippet for the selected rowClipParseReport.IsLosslessis just "any diagnostics at all"), so a harmless Info-level note looked as alarming as a real Error. Both now show a severity-appropriate glyph/color (gray "i" / orange "!" / red "✕"), and the panel itself sorts worst-severity-first with a breakdown header likeProblems (1 warning, 1 info)Test plan
dotnet test SharpFM.slnpasses (2275 tests)