roslyn-sdk
roslyn-sdk copied to clipboard
Roslyn-SDK templates and Syntax Visualizer
From #98: > Context menu is not themed
Version Used: 16.1 P1. No repro on 16.0 1. Open the syntax visualizer, and get it working (might require typing something in the editor) 2. Click somewhere outside the text...
Several strings in `AnalyzerTest` contain literal `\r\n` and/or `\n` characters. The analyzer testing library should be updated to consistently use `Environment.NewLine` where appropriate.
In the Syntax Visualizer, when you right-click on a syntax node, a context menu appears that lets you view semantic information about that node. But the context menu is not...
From #98: > The squiggle looks different depending on current scroll bar position (anti-aliasing behavior is imperfect)
From #98: https://github.com/dotnet/roslyn-sdk/blob/51a80120f263e2b6f0bc2b4e84738dd381b140c8/src/Tools/SyntaxVisualizer/Roslyn.SyntaxVisualizer.Control/SyntaxVisualizerControl.xaml#L78-L79 https://github.com/dotnet/roslyn-sdk/blob/51a80120f263e2b6f0bc2b4e84738dd381b140c8/src/Tools/SyntaxVisualizer/Roslyn.SyntaxVisualizer.Control/SyntaxVisualizerControl.xaml#L83-L86
Code fix tests involving multiple input documents may require a different number of Fix All iterations depending on the scope of the operation - especially for document vs. project scopes....
Currently the squiggle color used in Syntax Visualizer doesn't differentiate based on diagnostic severity. It should use appropriate colors for distinguishing errors and warnings, similar to what the editor does.
The subtitle for this repo that GitHub displays is out-dated. It should mention that the Roslyn analyzer/verifier testing framework is in it.
Currently the commit hash isn't present in the NuGet packages: https://dotnet.myget.org/feed/roslyn-analyzers/package/nuget/Microsoft.CodeAnalysis.Analyzer.Testing It would be nice to include it so it's clear where the code comes from.