Closed GoneZ5 closed 2 years ago
Hey, sorry for the delayed reply.
Sadly, this is actually a problem of unconventional handling of strings by tree-sitter for Go. Since the strings are represented
as interpreted_string_literal
instead of string
which breaks the string handling during tokenization.
In the current version, there is no easy workaround. However, I am working hard on version 0.2 which will make it much easier to integrate custom behavior for tokenization.
Should be closed in version 0.2.0. Please reopen if necessary.
Hi, when I parse the
go
function, the string value can not be parsed. Can you help me?Thank you in advance!