Repository navigation
Html Parser improvements #9340
Description
@laco0416 is working on making the interpolation config configurable in #9158.
Once this PR lands we can work on further Lexer/Parser improvements.
We should add a new INTERPOLATION_TOKEN to the lexer output for interpolations.
Benefits:
- Any character is allowed in an interpolation - currently
<in an interpolation is considered as a tag start and we backtrack on malformed track.a <b &c> dwould defeat our current strategy. (addresses in Improve lexers/parsers #9421) - There is currently no way to escape ICU messages (expansion forms) and interpolation. Because the lexer would be responsible for interpolation and expansion form, we can implement escaping by using
%xxfor those.
Activity
ajitsinghkaler commentedon Nov 24, 2019
@pkozlowski-opensource @gkalpak I think you can close this issue you have solved it.
angular-robot commentedon May 21, 2021
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
angular-robot commentedon Jun 10, 2021
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
angular-automatic-lock-bot commentedon Jul 12, 2021
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.