chore: stricter control flow syntax validation in runes mode #12342
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.
Handle whitespace characters between
{
and#
/:
/@
but disallow that in runes modecloses #11975
While implementing this I noticed that the else if block AST is too ambiguous right now. Is a fragment with a sole if block an else if or a if? it's indistinguishable, which is bad for formatting tools like prettier. We should change it to the if block AST being directly placed inside the alternate branch. Will do that if others agree as a follow-up once this is merged.
Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.Tests and linting
pnpm test
and lint the project withpnpm lint