You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Highlighting is broken for the generic parameter, which looks like it's treated as a JSX element.
Highlighting is broken for the function parameters, function body, and for the next function (it's broken for all following functions, I just included 1 in the example).
Surprisingly (to me 😄), the behavior is affected by the name of the generic variable. If I use T instead of K, I get this:
Highlighting for the generic parameter is still broken, but in a different way than above. Now it's all the default text color.
Highlighting is correct for the function parameters, function body, and the following function(s).
For simple generics, I can get away with just using T for now, but that's not always the best type variable to use, doesn't cover functions that need more than one generic parameter, and is still missing highlighting for the type parameters themselves.
The text was updated successfully, but these errors were encountered:
I'm running into inconsistencies in highlighting between
ft=typescript
andft=typescriptreact
.I'm using
yats.vim
,vim-javascript
, and of coursevim-jsx-pretty
, all just updated usingvim-plug
.Some example code:
When filetype is

typescript
:When filetype is

typescriptreact
:Surprisingly (to me 😄), the behavior is affected by the name of the generic variable. If I use

T
instead ofK
, I get this:For simple generics, I can get away with just using
T
for now, but that's not always the best type variable to use, doesn't cover functions that need more than one generic parameter, and is still missing highlighting for the type parameters themselves.The text was updated successfully, but these errors were encountered: