Closed vmarkovtsev closed 4 years ago
Yeah, I know where it comes from. The uast:QualifiedIdentifier
is synthesized by splitting the import path, so we don't really have those positions from the parser. But it's easy to synthesize positions as well.
cc @r0mainK
Very cool, will check if it changes anything when I can
Consider this code:
Each leaf in the tree of type
uast:Identifier
has a Position, but it is not filled. The parentuast:QualifiedIdentifier
has it filled, however.