Skip to content
This repository was archived by the owner on May 12, 2025. It is now read-only.

No Semicolon for J.Unknown and no unnecessary JS.ExpressionStatement#124

Merged
knutwannheden merged 1 commit intomainfrom
parser-fixes
Oct 8, 2024
Merged

No Semicolon for J.Unknown and no unnecessary JS.ExpressionStatement#124
knutwannheden merged 1 commit intomainfrom
parser-fixes

Conversation

@knutwannheden
Copy link
Copy Markdown
Contributor

A J.Unknown inside a JRightPadded doesn't need any Semicolon, as the J.Unknown will already contain the semicolon in its source.

Also, the parser should not produce any unnecessary JS.ExpressionStatements, as visitors like the visitor implementation in Java will automatically remove that and thus cause the tree to change.

…ment`

A `J.Unknown` inside a `JRightPadded` doesn't need any `Semicolon`, as the `J.Unknown` will already contain the semicolon in its source.

Also, the parser should not produce any unnecessary `JS.ExpressionStatement`s, as visitors like the visitor implementation in Java will automatically remove that and thus cause the tree to change.
@knutwannheden knutwannheden merged commit 29511db into main Oct 8, 2024
@knutwannheden knutwannheden deleted the parser-fixes branch October 8, 2024 15:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant