-
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
Remove reverse! call for timezone after converting structure to hash #14772
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Checked commit gmcculloug@d7bb1da with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
simaishi
pushed a commit
that referenced
this pull request
Apr 19, 2017
Remove reverse! call for timezone after converting structure to hash (cherry picked from commit e761f4b) https://bugzilla.redhat.com/show_bug.cgi?id=1443247
Fine backport details:
|
simaishi
pushed a commit
that referenced
this pull request
May 4, 2017
Remove reverse! call for timezone after converting structure to hash (cherry picked from commit e761f4b) https://bugzilla.redhat.com/show_bug.cgi?id=1443248
Euwe backport details:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the list of Timezones used with the VMware customization spec were stored as an array to maintain order before hashes were guaranteed to return in the order of insertion. Now the provisioning workflow can use a hash which matches the structure used by most of the
allowed_*
methods in the request workflow classes.This allows us to treat the data in the UI like other fields (ManageIQ/manageiq-ui-classic#982) and requires less data manipulation like the
.collect(&:reverse)
call in ManageIQ/manageiq-providers-vmware#35 and the change in this PR.Changing the
get_timezones
method to return a hash allows data passed during an API call to be processed like other fields which resolves the reported issue.Ultimately the customization spec logic needs to be refactored to live in the vmware repo but that is outside of the scope of this bug fix.
Links
Steps for Testing/QA
See https://bugzilla.redhat.com/show_bug.cgi?id=1406084
cc @d-m-u @himdel