-
Notifications
You must be signed in to change notification settings - Fork 26.6k
fix(migrations): handle empty ngSwitchCase #56105
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
Do you mind bringing in the test you had in #56103, thank you ? |
main branch didnt contain test file for control flow migration, so im not sure where that test would go. |
Oh it looks like the file was (mistakenly ?) removed in #55391 |
isnt it more like we dont need those tests anymore as it just works - like we wouldnt be needing that migration in v18 as it was for migrating from v17 to v18, now we are just providing fixes for missing cases? apologies if i misunderstood something! take my word for it, it works on my PC! 😀 |
Definitely those tests need to be restored! |
This migration was optional in v17 as control flow was still in developer preview. |
should i bring them back in this branch or create new one? |
I'll create a PR to restore the tests. |
Looks like @alan-agius4 beat me to it with #56130. |
@naaajii the PR restoring the tests has been merged. Can you rebase and add your test case? |
empty ngSwitchCase generate `case ()` which isn't valid syntax therefore adding quotes will help prevent us migrate empty case if no condition was provided fix angular#56030
done! |
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.
LGTM! Thanks for updating this!
This PR was merged into the repository by commit 3b2f88c. |
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. |
empty ngSwitchCase generate
case () {
which isn't valid syntax therefore adding quotes will help prevent us migrate empty case if no condition was providedfix #56030
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: #56030
control flow cases being generated with no fallback value in them
What is the new behavior?
control flow cases contain single quotes if ngSwitchCase didnt had any value in it
Does this PR introduce a breaking change?
Other information