refactor: use officially supported strict_templates attribute on ng_module() and remove local workaround
#23677
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g_module()` and remove local workaround Refs: angular/angular#33452. This workaround is no longer necessary since `ng_module()` actually supports strict templates now (see angular/angular#43582).
google-cla
bot
added
the
cla: yes
5 tasks
|
The desired change here got included in #23689. The strict templates patch is removed and Nothing more to do here. |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Refs: angular/angular#33452.
This workaround is no longer necessary since
ng_module()actually supports strict templates now (see angular/angular#43582).Creating this PR as a draft right now as it is blocked on components upgrading to
@angular/[email protected]or later.