-
Notifications
You must be signed in to change notification settings - Fork 897
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
[GAPRINDASHVILI] fixed saving tag name #18386
[GAPRINDASHVILI] fixed saving tag name #18386
Conversation
closed in favor of #18387 |
@miq-bot remove-label hammer/yes |
5d2d95b
to
359f671
Compare
app/models/classification.rb
Outdated
@@ -525,7 +525,12 @@ def find_tag | |||
end | |||
|
|||
def save_tag | |||
self.tag = Tag.find_or_create_by_classification_name(name, region_id, ns, parent_id) | |||
tag_name = Classification.name2tag(name, parent_id, ns) |
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.
Small nit but, couldn't this line be moved into the if
block?
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.
sure, it is leftover from my "backporting" from master where tag_name
used in else
block too
Checked commits yrudman/manageiq@00a6a3c~...5512d1c with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
…aving-tag-name" This reverts commit ac3a51e, reversing changes made to 5d837f5. https://bugzilla.redhat.com/show_bug.cgi?id=1668730
This is now reverted:
|
Issue: Editing tag name on existing record creates new record in Tag table
Fix: Do not create new record in Tag table when editing existing tag
Backport of #18378
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1668730
@miq-bot add-label core, bug, gaprindashvili/yes, hammer/yes