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

Replace 'values' key with 'default_value' when updating value for field #384

Merged
merged 1 commit into from May 8, 2019

Conversation

eclarizio
Copy link
Member

@eclarizio eclarizio commented May 6, 2019

@eclarizio eclarizio force-pushed the fix_for_dynamic_non_sorted_items branch from 5eff211 to 7dcb1f7 Compare May 6, 2019 21:20
@miq-bot miq-bot added the bug label May 6, 2019
@miq-bot
Copy link
Member

miq-bot commented May 6, 2019

Checked commit eclarizio@7dcb1f7 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
0 files checked, 0 offenses detected
Everything looks fine. 🏆

Copy link
Contributor

@d-m-u d-m-u left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

@tinaafitz
Copy link
Member

tinaafitz commented May 8, 2019

@Fryguy Can you merge this PR? Brno is on holiday today and this change is needed for several high severity issues.

@Fryguy Fryguy merged commit 578c154 into ManageIQ:master May 8, 2019
@himdel himdel added this to the Sprint 111 Ending May 13, 2019 milestone May 10, 2019
@simaishi
Copy link

@eclarizio I assume this is hammer/yes?

@eclarizio
Copy link
Member Author

@simaishi Yeah, you're correct.

@miq-bot add_label hammer/yes

@tinaafitz
Copy link
Member

tinaafitz commented May 15, 2019

@simaishi
Copy link

Hammer backport details:

$ git log -1
commit 65ad1c7e7933096547863e5c42d0d6364bfa8864
Author: Jason Frey <fryguy9@gmail.com>
Date:   Wed May 8 12:30:44 2019 -0400

    Merge pull request #384 from eclarizio/fix_for_dynamic_non_sorted_items
    
    Replace 'values' key with 'default_value' when updating value for field
    
    (cherry picked from commit 578c154c3e3846f251e9c065ac11f38a5d187c7b)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1710578
    https://bugzilla.redhat.com/show_bug.cgi?id=1710606
    https://bugzilla.redhat.com/show_bug.cgi?id=1710608
    https://bugzilla.redhat.com/show_bug.cgi?id=1710610

@simaishi
Copy link

@himdel Can you please release a new version of ui-components for this change for hammer branch?

@simaishi
Copy link

FYI, Travis is red on hammer for yet another 'node' incompatible error:
https://travis-ci.org/ManageIQ/ui-components/builds/533011740

error jsdoc@3.6.2: The engine "node" is incompatible with this module. Expected version ">=8.15.0".
error Found incompatible module

@himdel
Copy link
Contributor

himdel commented May 16, 2019

Released in 1.1.26, and I think backporting #361 is probably the best way to fix travis after all..

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.

None yet

7 participants