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
.
Alright, given the following snippet, the . will actually be marked as a number.
number
val myList = List(1, 2, 3) myList .map(_ * 2) // <- . here is marked as a number
A corpus for this bug would look like this:
=============================== Chained expressions =============================== def main() { val myList = List(1, 2, 3) myList.map(_ * 2) myList .map(_ * 2) } --- (compilation_unit (function_definition (identifier) (parameters) (block (val_definition (identifier) (call_expression (identifier) (arguments (number) (number) (number)))) (call_expression (field_expression (identifier) (identifier)) (arguments (infix_expression (identifier) (operator_identifier) (number)))) (call_expression (field_expression (identifier) (identifier)) (arguments (infix_expression (identifier) (operator_identifier) (number)))))))
You can see what it actually does here:
I think this is actually a automatic semi insertion issue where we don't account that the .call can be on a new line.
.call
The text was updated successfully, but these errors were encountered:
Add recognition of multi-line field expression (tree-sitter#23)
3bc5cbd
21c5277
Add recognition of multi-line field expression (#23) (#32)
449b6ba
@maxbrunsfeld I think we can close this one.
Sorry, something went wrong.
No branches or pull requests
Alright, given the following snippet, the
.
will actually be marked as anumber
.A corpus for this bug would look like this:
You can see what it actually does here:
I think this is actually a automatic semi insertion issue where we don't account that the
.call
can be on a new line.The text was updated successfully, but these errors were encountered: