-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Template string highlighting and export default interface highlight #64
base: master
Are you sure you want to change the base?
Changes from all commits
1f0def9
91e0d4d
7bd018f
c431dca
96e78be
3778f88
67810dc
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 |
---|---|---|
|
@@ -23,6 +23,8 @@ syntax region typescriptTemplate | |
\ nextgroup=@typescriptSymbols | ||
\ skipwhite skipempty | ||
|
||
syntax match typescriptTaggedTemplate /\<\K\k*\ze`/ nextgroup=typescriptTemplate | ||
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. Please don't do this. It will overlap with typescriptIdentifier and make backtracking more often. It also doesn't handle case like funcCall()`` 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. Ah, I think I'm at the limit of my vim syntax knowledge then so I'm not sure where to put it :-). So far I'm using it and the funcCall()`` case gets handled tho. Must be handled by the usual typescriptTemplate match. |
||
|
||
"Array | ||
syntax region typescriptArray matchgroup=typescriptBraces | ||
\ start=/\[/ end=/]/ | ||
|
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.
This is a good fix! Thanks!