Skip to content

fix(compiler): produce less noisy errors when parsing control flow #57711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 7, 2024

Currently several parsing errors in the new control flow (e.g. missing track expression) produce errors whose span targets the entire block. This can be really noisy in the IDE where the error can span many lines in the template.

These changes switch to highlighting just the start of the block.

Currently several parsing errors in the new control flow (e.g. missing `track` expression) produce errors whose span targets the entire block. This can be really noisy in the IDE where the error can span many lines in the template.

These changes switch to highlighting just the start of the block.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Sep 7, 2024
@crisbeto crisbeto requested a review from devversion September 7, 2024 07:01
@angular-robot angular-robot bot added the area: compiler Issues related to `ngc`, Angular's template compiler label Sep 7, 2024
@ngbot ngbot bot added this to the Backlog milestone Sep 7, 2024
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 7, 2024
thePunderWoman pushed a commit that referenced this pull request Sep 9, 2024
…57711)

Currently several parsing errors in the new control flow (e.g. missing `track` expression) produce errors whose span targets the entire block. This can be really noisy in the IDE where the error can span many lines in the template.

These changes switch to highlighting just the start of the block.

PR Close #57711
@thePunderWoman
Copy link
Contributor

This PR was merged into the repository by commit 40ff18f.

The changes were merged into the following branches: main, 18.2.x

and-oli pushed a commit to and-oli/angular that referenced this pull request Sep 30, 2024
…ngular#57711)

Currently several parsing errors in the new control flow (e.g. missing `track` expression) produce errors whose span targets the entire block. This can be really noisy in the IDE where the error can span many lines in the template.

These changes switch to highlighting just the start of the block.

PR Close angular#57711
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: compiler Issues related to `ngc`, Angular's template compiler target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants