(PR for this issue that was already in progress - to be tackled in a future sprint)
The tests for the TokenTypeAnalyzer could be more precise. They only assert the number of tokens per type found in a code snippet. We need a more precise way to assert the token type. The best way is to annotate the code snippet with the expected token type and position. This PR adds a small test harness with support for [x:SomeToken] syntax, where x corresponds to the TokenType enum defined by the protobuf contract like so:
A code snippet like
can be annotated and asserted like so:
public [k:class] [t:Test]
{
}
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4