We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
tree-sitter --version
tree-sitter 0.20.9
Currently there is a mismatch between the local parsing using tree-sitter-typescript and using the online playground.
tree-sitter-typescript
File I am testing can be found here.
The local version give me an error, with an exit code 1, while online playground works as expected.
(ERROR [0, 0] - [2658, 0] (comment [0, 0] - [6, 3]) (import_statement [7, 0] - [7, 95] (import_clause [7, 7] - [7, 67] (named_imports [7, 7] - [7, 67] (import_specifier [7, 8] - [7, 15] name: (identifier [7, 8] - [7, 15])) (import_specifier [7, 17] - [7, 31] name: (identifier [7, 17] - [7, 31])) (import_specifier [7, 33] - [7, 38] .......
tree-sitter parse '....angular/packages/core/test/acceptance/integration_spec.ts'
Get parsed like in the playground
// Cannot add one: `There was an error creating your issue: body is too long (maximum is 65536 characters).` Just use the links added above
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Did you check existing issues?
Tree-Sitter CLI Version, if relevant (output of
tree-sitter --version
)tree-sitter 0.20.9
Describe the bug
Currently there is a mismatch between the local parsing using
tree-sitter-typescript
and using the online playground.File I am testing can be found here.
The local version give me an error, with an exit code 1, while online playground works as expected.
Steps To Reproduce/Bad Parse Tree
tree-sitter parse '....angular/packages/core/test/acceptance/integration_spec.ts'
Expected Behavior/Parse Tree
Get parsed like in the playground
Repro
The text was updated successfully, but these errors were encountered: