fix: handle decorators after type declarations #21
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.
Issue: #20
Problem:
The parser crashes with Unexpected character '@' when a decorator appears immediately after an interface or type declaration, which is common in Angular and NestJS codebases.
Example:
Root cause
After parsing the interface closing
}, the parser callsnext()to advance to the@character while still in type parsing mode. ThegetTokenFromCodeInTypemethod didn't handle@, causing it to fall through to the base parser which doesn't recognise decorators.Solution
Added
@character handling ingetTokenFromCodeInTypemethod moving the position of the cursor and finishing by callingfinishTokenwith the token type@Testing