-
Notifications
You must be signed in to change notification settings - Fork 20
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
Julia TS node names have changed #38
Comments
Yea, feel free to make a PR and I'll merge. I'm not familiar with Julia so I personally won't be putting up a fix. cc @timoleistner who originally added Julia support. |
Update julias treesitter node names according to RRethy#38 Added additional node names too.
Since it's been a while and @ArbitRandomUser did not create a pull request, I've done it.
This does happen no matter where I do this in my code. Please let me know if I should create a separate issue or if you need more information. |
That would indicate your Julia parser may be out of date. |
fixed it :) |
* Update treesitter node names Update julias treesitter node names according to #38 Added additional node names too. * fixes E5108 invalid node type at position 2 for language julia
was waiting for you to chime in @timoleistner, your fix is neat and more comprehensive than mine. |
bumping because i dont want to make a new issue for this , |
Created a pull request for let statements.
|
@timoleistner it seems the TS node names have been slightly modified again , |
I'm not sure why , but right now julia textsubjects is broken.
it looks like the node names are different , changing to appropriate node names in the queries scm seems to make it work.
comment
is nowline_comment
array_expression
is nowvector_expression
,i dont have much of an idea on Treesitter, but i can make a PR with the changes that i did to get it working , may i ?
The text was updated successfully, but these errors were encountered: