Did you check the tree-sitter docs?
Is your feature request related to a problem? Please describe.
String start and string end are not anonymous. The Tree-sitter documentation suggest to ignore anonymous nodes to seek in the tree as an abstract syntax tree. Mileage may vary, but I personally don’t see a place for these in an abstract syntax.
Describe the solution you'd like
Make string_start and string_end, anonymous.
Describe alternatives you've considered
It is possible to filter to interpret these nodes as anonymous, even if they are not.
Additional context
I don’t know if the author of the Python syntax would agree. The string enclosing form is used to distinguish doc-strings, but the python tree-sitter does not apply this distinction. Or if this distinction is to be applied, then make an abstract node for this, but still without considering the opening and the closing of a string, as abstract.
Did you check the tree-sitter docs?
Is your feature request related to a problem? Please describe.
String start and string end are not anonymous. The Tree-sitter documentation suggest to ignore anonymous nodes to seek in the tree as an abstract syntax tree. Mileage may vary, but I personally don’t see a place for these in an abstract syntax.
Describe the solution you'd like
Make string_start and string_end, anonymous.
Describe alternatives you've considered
It is possible to filter to interpret these nodes as anonymous, even if they are not.
Additional context
I don’t know if the author of the Python syntax would agree. The string enclosing form is used to distinguish doc-strings, but the python tree-sitter does not apply this distinction. Or if this distinction is to be applied, then make an abstract node for this, but still without considering the opening and the closing of a string, as abstract.