Closed serranomorante closed 7 months ago
Opened an issue here: https://github.com/nvim-treesitter/nvim-treesitter/issues/6202 with a related bug
Opened an issue here: nvim-treesitter/nvim-treesitter#6202 with a related bug
From that issue:
This is a parser issue; nothing we can do here.
although it's fixed in jsx which is where the issue lies, it's not exactly fixed here yet, i probably will update parser.c within a couple hrs here as well
although it's fixed in jsx which is where the issue lies, it's not exactly fixed here yet, i probably will update parser.c within a couple hrs here as well
Thank you so much! 🤗
although it's fixed in jsx which is where the issue lies, it's not exactly fixed here yet, i probably will update parser.c within a couple hrs here as well
Sorry for the basic question but I just realized that the fix on tree-sitter-javascript
also fixes the issue here on the tree-sitter-typescript
parser automatically? Then why would you need to update this repo's parser.c
file?
jajaja I'm so sorry! my previous comment doesn't make any sense. It was because I had treesitter highlight disabled, now that I enabled it again the issue remains for typescript and tsx files.
ok this is actually fixed in typescript as well now, sorry for forgetting to bump js
ok this is actually fixed in typescript as well now, sorry for forgetting to bump js
No worries! Thank you, it is working now! 👍
Did you check existing issues?
Tree-Sitter CLI Version, if relevant (output of
tree-sitter --version
)No response
Describe the bug
Only happens on
repro.tsx
file but not onrepro.ts
file.Ampersand should be a perfectly valid char on a className=string but it is breaking syntax highlighting.
Steps To Reproduce/Bad Parse Tree
tsx
treesitter parserExpected Behavior/Parse Tree
Syntax highlighting shouldn't break on
*.tsx
files using thetsx
parserRepro