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
One thing I've noticed is that when using TS/JS files, the entirety of the contents of template literal strings are in italics which makes it a little difficult to read at times:
I wonder if this is an intentional choice or if there is a way of of doing something different in named template literals, where the content is often HTML templates as strings?
The text was updated successfully, but these errors were encountered:
benfrain
changed the title
Entirety of JS/TS template literal is italic
Entirety of JS/TS named template literal is italic
Feb 17, 2022
Thanks for reporting, that's definitely not intentional. Ideally, we want to handle tagged templates differently. Do you have an insight on how to achieve that? Maybe we have to adjust something upstream in https://github.com/nvim-treesitter/nvim-treesitter?
It seems it's treated as a normal string in nvim-treesitter. I wonder if we can adjust the query to treat it as TSStringSpecial instead so that we can assign a more specific hl group (one that is without italic).
mcchrish
changed the title
Entirety of JS/TS named template literal is italic
Entirety of JS/TS tagged template literal is italic
Feb 18, 2022
Thanks for zenbones!
One thing I've noticed is that when using TS/JS files, the entirety of the contents of template literal strings are in italics which makes it a little difficult to read at times:
For comparison here is the same thing in nightfox
I wonder if this is an intentional choice or if there is a way of of doing something different in named template literals, where the content is often HTML templates as strings?
The text was updated successfully, but these errors were encountered: