-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
fix(migrations): Add missing support for ngForOf #52903
Conversation
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow.
f6a4b3b
to
1fa385a
Compare
@@ -12,6 +12,12 @@ import {ElementCollector, ElementToMigrate, MigrateError, Result} from './types' | |||
import {calculateNesting, getMainBlock, getOriginals, hasLineBreaks, parseTemplate, reduceNestingOffset} from './util'; | |||
|
|||
export const ngfor = '*ngFor'; | |||
export const nakedngfor = 'ngFor'; | |||
const fors = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And also with you, @JoostK. :D
This PR was merged into the repository by commit 8f5124e. |
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow. PR Close #52903
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow. PR Close angular#52903
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. |
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow. PR Close angular#52903
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow. PR Close angular#52903
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow. PR Close angular#52903
This adds support to migrate ngForOf and ngForTrackBy when migrating control flow.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?