-
Notifications
You must be signed in to change notification settings - Fork 26.2k
feat(compiler): support skipping leading trivia in the lexer #30095
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
Conversation
b62e895
to
ed8d1d2
Compare
Leading trivia, such as whitespace or comments, is confusing for developers looking at source-mapped templates, since they expect the source-map segment to start after the trivia. This commit adds skipping trivial characters to the lexer; and then implements that in the template parser.
ed8d1d2
to
26fdcb4
Compare
@petebacondarwin this PR had conflicts while merging into patch branch, so I merged it to master only. Could you please create a separate PR with the necessary changes against patch branch? Thank you. |
@AndrewKushnir - thanks I mistakenly marked if for both master and patch. But it should have only been master. |
…ps (angular#30095) Leading trivia, such as whitespace or comments, is confusing for developers looking at source-mapped templates, since they expect the source-map segment to start after the trivia. This commit adds skipping trivial characters to the lexer; and then implements that in the template parser. PR Close angular#30095
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Leading trivia, such as whitespace or comments, is
confusing for developers looking at source-mapped
templates, since they expect the source-map segment
to start after the trivia.
This commit add skipping this trivia to the Angular lexer.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information