Fixing the parsing of class names #17
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
The old version of the parser was looking for the class keyword followed by a
{
. The problem is the parser doesn't take into account that the class keyword can also be used in a different context like inself::class
which then will crash because if you have something like expression likethis it will take the token that is two after the class keyword which in this case would be the semicolon. Which is not correct.
What?
I have added a check that if the token preceding the class keyword is the '::' operator, then it will skip it. (It's not a good fix though).
Further things to consider