Skip to content

Handle records in syntax highlighting#2049

Merged
filipw merged 1 commit intoOmniSharp:masterfrom
333fred:fix-record-highlight
Dec 27, 2020
Merged

Handle records in syntax highlighting#2049
filipw merged 1 commit intoOmniSharp:masterfrom
333fred:fix-record-highlight

Conversation

@333fred
Copy link
Copy Markdown
Contributor

@333fred 333fred commented Dec 22, 2020

Fixes #2048.

@333fred 333fred force-pushed the fix-record-highlight branch from b05c01b to 6321175 Compare December 22, 2020 18:59
@333fred
Copy link
Copy Markdown
Contributor Author

333fred commented Dec 22, 2020

@JoeRobich for review.

[ClassificationTypeNames.VerbatimStringLiteral] = SemanticHighlightClassification.VerbatimStringLiteral,
[ClassificationTypeNames.StringEscapeCharacter] = SemanticHighlightClassification.StringEscapeCharacter,
[ClassificationTypeNames.ClassName] = SemanticHighlightClassification.ClassName,
[ClassificationTypeNames.RecordName] = SemanticHighlightClassification.ClassName,
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other option would be to map a separate classification for record names and have the clients deal with it. Which is fine, just need to know what to do.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, this is fine IMHO

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, the only concern is that we'll need to do something different when struct records come out, but that's a concern for next year :).

@filipw filipw merged commit 8f3b6ea into OmniSharp:master Dec 27, 2020
@333fred 333fred deleted the fix-record-highlight branch December 27, 2020 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Records break syntax highlighting

2 participants