-
Notifications
You must be signed in to change notification settings - Fork 898
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
Imports old associations #16471
Imports old associations #16471
Conversation
@miq-bot assign @gmcculloug |
@eclarizio can you review, pretty please? |
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.
Think you can add a spec around the other "associations" spec (on master it's at line 187) that actually checks to make sure the right association was made? That's the whole point of doing the .position
and everything, so I feel like it would be good to have a spec around it.
d3f0dcb
to
bc87471
Compare
bc87471
to
83106af
Compare
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.
👍
Checked commit d-m-u@83106af with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@miq-bot add_label gaprindashvili/yes |
thanks @eclarizio ✨ |
Imports old associations (cherry picked from commit 6edddb7)
Gaprindashvili backport details:
|
This extends the dialog field association import code to also deal with the now-defunct associations listed as trigger_auto_refresh and auto_refresh. It's the same code as the recent data migration that does this import and should allow people to import old dialogs and have the associations converted to use the new table.