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

Fixed undefined method `each' for nil:NilClass error on retirement tab #762

Merged
merged 1 commit into from
Mar 22, 2017

Conversation

h-kataria
Copy link
Contributor

Now that retirement hash is returned with remove_resources value, had to add checks around extra_vars loops to fix undefined method `each' for nil:NilClass error. And also only show Dialog name/link if dialog was selected on retirement tab.

@gmcculloug please review, i was seeing this error while accessing catalog item that i had save Remove Resources value for.

Now that retirement hash is returned with remove_resources value, had to add checks around extra_vars loops to fix undefined method `each' for nil:NilClass error. And also only show Dialog name/link if dialog was selected on retirement tab.
@miq-bot
Copy link
Member

miq-bot commented Mar 21, 2017

Checked commit h-kataria@0c890d1 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 1 offense detected

app/views/catalog/_sandt_tree_show.html.haml

  • ⚠️ - Line 324 - Avoid more than 3 levels of block nesting.

@gmcculloug
Copy link
Member

@tinaafitz Please review.

@tinaafitz
Copy link
Member

@h-kataria Looks good.

@h-kataria
Copy link
Contributor Author

@martinpovolny @mzazrivec please merge

@mzazrivec mzazrivec self-assigned this Mar 22, 2017
@mzazrivec mzazrivec added this to the Sprint 57 Ending Mar 27, 2017 milestone Mar 22, 2017
@mzazrivec mzazrivec merged commit 67a0c0a into ManageIQ:master Mar 22, 2017
@h-kataria h-kataria deleted the fix_undefined_method_error branch April 4, 2017 18:41
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