-
Notifications
You must be signed in to change notification settings - Fork 356
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
Clear out all dialog resources before adding/validating. #1306
Clear out all dialog resources before adding/validating. #1306
Conversation
2bf1ee7
to
fde8643
Compare
Clear out all dialog resources to make sure there is no invalid resources left from previous invalid transaction. https://bugzilla.redhat.com/show_bug.cgi?id=1448274
fde8643
to
b66aa8d
Compare
Checked commit h-kataria@b66aa8d with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Looks good - verified in the UI |
@chessbyte can you please merge |
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.
The only thing I'm concerned about here is the test. Doing a lot of instance_variable_set
s feels a little dirty and that means maybe something needs to be broken out. It is also really long and has a lot of steps in a single it
block. It feels more like an acceptance test than a unit test, and I think because of that, again points to some refactoring that could be done. I don't think it's 100% necessary to do it in this PR, but I think it's a good thing to keep in mind going forward.
Clear out all dialog resources before adding/validating. (cherry picked from commit 91a9c32) https://bugzilla.redhat.com/show_bug.cgi?id=1448943
Fine backport details:
|
Clear out all dialog resources to make sure there is no invalid resources left from previous invalid transaction.
https://bugzilla.redhat.com/show_bug.cgi?id=1448274
@lgalis @eclarizio please test/review.