-
Notifications
You must be signed in to change notification settings - Fork 1
Refactor how we're doing semantic highlighting and highlight left side of editor #47
New issue
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,5 +3,5 @@ namespace NetStackBeautifier.Core | |
| /// <summary> | ||
| /// A parameter. | ||
| /// </summary> | ||
| public record FrameParameter(string ParameterType, string ParameterName); | ||
| public record FrameParameter(string ParameterType, string ParameterName, string RawParameterType, string FullParameterName); | ||
|
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What is
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We do some transformations on the parameter names depending on the types. For example |
||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between
RawGenericParameterTypescompare toGenericParameterTypes?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I mentioned below this simple includes the unprocessed
GenericParameterTypesso that the pre-beautified stack can be highlighted correctly. The idea is to piggyback off the parsing we're doing for the beautification, otherwise we'd be essentially re-parsing the callstack from our extension to determine the semantic highlighting rules.It could certainly be more intuitive though, maybe all of the parsed entities should simple return a
Beautified{Entity}and aFull{Entity}where Entity is a generic parameter type, method param, etc.