Skip to content
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

Make cascading auto-refresh behavior more consistent with how it was previously #433

Merged

Conversation

eclarizio
Copy link
Member

This forces triggering of fields set to auto-refresh in order to stay consistent with the behavior prior to the cascading change.

The reasoning is that previously, if we had 1 field set to trigger and 4 set to listen, all 4 would get updated, but with the new cascading changes, the 4 set to listen would need to be set to also trigger. This fix will ensure that all 4 will update even if they are not set to trigger.

@miq-bot add_label darga/yes euwe/yes
@miq-bot assign @gmcculloug

@gmcculloug Please re-assign as necessary and/or tag people for review.

@miq-bot
Copy link
Member

miq-bot commented Feb 20, 2017

@eclarizio Cannot apply the following label because they are not recognized: darga/yes euwe/yes

@miq-bot
Copy link
Member

miq-bot commented Feb 20, 2017

@eclarizio @gmcculloug is an invalid assignee, ignoring...

@eclarizio
Copy link
Member Author

@miq-bot add_label darga/yes, euwe/yes

@miq-bot
Copy link
Member

miq-bot commented Feb 20, 2017

Checked commit eclarizio@04bf1fb with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
4 files checked, 0 offenses detected
Everything looks good. 🍰

@gmcculloug
Copy link
Member

@dclarizio Tested changes. Looks good.

@simaishi
Copy link
Contributor

Backported to Euwe via ManageIQ/manageiq#13994

@simaishi
Copy link
Contributor

Backported to Darga via ManageIQ/manageiq#13993

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants