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
In the current approach (not yet merged to master), the token type analyzer currently maps back tokens from the generated source to the razor source.
This approach is an effective first baby step to provide quick support for Razor syntax highlighting, but comes with some limitations:
@using
@page
@*
The alternative, and the goal of this task, is to have a Razor-specific implementation of the TokenTypeAnalyzer that uses RazorSyntaxTree.
TokenTypeAnalyzer
See razor unit tests on tokenization (some examples here) for some examples of its use.
That would generate all types of tokens, since Razor tokens embed C# ones: see here.
Disadvantages:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the current approach (not yet merged to master), the token type analyzer currently maps back tokens from the generated source to the razor source.
This approach is an effective first baby step to provide quick support for Razor syntax highlighting, but comes with some limitations:
@using
,@page
,@*
etc.) are not supportedThe alternative, and the goal of this task, is to have a Razor-specific implementation of the
TokenTypeAnalyzer
that uses RazorSyntaxTree.See razor unit tests on tokenization (some examples here) for some examples of its use.
That would generate all types of tokens, since Razor tokens embed C# ones: see here.
Disadvantages:
The text was updated successfully, but these errors were encountered: