We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug: In VSCode, Razor syntax highlighting is broken when using nullable operator "?"
Version used: VSCode 1.69.2 .Net 7.0.100-preview.6.22352.1
To reproduce: Open the following in VSCode
@Param1 @Param2 @code { [Parameter] public string? Param1 { get; set; } [Parameter] public string? Param2 { get; set; } private string Foo() { return "bar"; } }
Expected behavior: Razor syntax highlighting should work as expected when using nullable operator "?" (see screenshot 1)
Actual behavior: Razor syntax highlighting is broken when using nullable operator "?" (see screenshot 2)
Additional context:
Screenshot 1 - Syntax highlighting working when not using nullable operator
Screenshot 2 - Syntax highlighting not working when using nullable operator
The text was updated successfully, but these errors were encountered:
Additional report: #6144
Sorry, something went wrong.
Additional report: #7076
Additional report: #8184
Successfully merging a pull request may close this issue.
Describe the bug:
In VSCode, Razor syntax highlighting is broken when using nullable operator "?"
Version used:
VSCode 1.69.2
.Net 7.0.100-preview.6.22352.1
To reproduce:
Open the following in VSCode
Expected behavior:
Razor syntax highlighting should work as expected when using nullable operator "?" (see screenshot 1)
Actual behavior:
Razor syntax highlighting is broken when using nullable operator "?" (see screenshot 2)
Additional context:
Screenshot 1 - Syntax highlighting working when not using nullable operator
Screenshot 2 - Syntax highlighting not working when using nullable operator
The text was updated successfully, but these errors were encountered: