Introduce new nodeRange field in Node. As far as I know, all the parsers that we use support the positions of the beginning and end of the code for any vertex that this code represents, so it is logical to collect this information as well. This PR achieves this by adding new field in Node abstract class and by adding partial support for this extraction (only for Java parsers).
Refactor token handling logic by extracting it into a separate class Token
Do the same with Normalization (extract and clarify which normalization we are actually using)
nodeRangefield inNode. As far as I know, all the parsers that we use support the positions of the beginning and end of the code for any vertex that this code represents, so it is logical to collect this information as well. This PR achieves this by adding new field inNodeabstract class and by adding partial support for this extraction (only for Java parsers).TokenNormalization(extract and clarify which normalization we are actually using)