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

[EUWE] correct field names in reports #15498

Merged
merged 2 commits into from
Jul 7, 2017
Merged

[EUWE] correct field names in reports #15498

merged 2 commits into from
Jul 7, 2017

Conversation

jntullo
Copy link

@jntullo jntullo commented Jul 3, 2017

Euwe version of #14905

Needed to add a couple of missing elements (REGEX and parse_params) to resolve conflicts and make this work. Tried to cherry pick as little as possible from the latest implementation of MiqExpression and only take what was necessary to get it to work as expected while fixing the BZ.

@miq-bot add_label euwe/yes, bug

Screenshot of the report after this fix - properly colors the "Approved by" column
screen shot 2017-07-03 at 11 48 28 am

@jntullo
Copy link
Author

jntullo commented Jul 3, 2017

@miq-bot add_label wip

@miq-bot miq-bot changed the title [EUWE] correct field names in reports [WIP] [EUWE] correct field names in reports Jul 3, 2017
@miq-bot miq-bot added the wip label Jul 3, 2017
@miq-bot
Copy link
Member

miq-bot commented Jul 3, 2017

Checked commits jntullo/manageiq@0f977e1~...ced36f0 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
7 files checked, 0 offenses detected
Everything looks fine. ⭐

@jntullo
Copy link
Author

jntullo commented Jul 3, 2017

@miq-bot remove_label wip

@miq-bot miq-bot changed the title [WIP] [EUWE] correct field names in reports [EUWE] correct field names in reports Jul 3, 2017
@miq-bot miq-bot removed the wip label Jul 3, 2017
@djberg96
Copy link
Contributor

djberg96 commented Jul 6, 2017

Random comments from left field, I know!

The specs could use some love IMO, specifically the Tag::REGEX. It's always good to ensure that the regex matches what you think it matches. I'm curious why it's Tag::REGEX but Field::FIELD_REGEX. Not a big deal, just wondering if there's some standard we should be adhering to.

BTW, the current failure seems to be a Travis job issue, not an issue with the PR.

Copy link
Member

@gtanzillo gtanzillo left a comment

Choose a reason for hiding this comment

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

This LGTM 👍 @imtayadeway, can you give this a once over?

@simaishi simaishi requested a review from imtayadeway July 7, 2017 12:33
@@ -12,7 +12,7 @@ class MiqExpression::Field
ParseError = Class.new(StandardError)

def self.parse(field)
match = FIELD_REGEX.match(field) or raise ParseError, field
Copy link
Contributor

Choose a reason for hiding this comment

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

Was this to fix a rubocop complaint? I wish it wouldn't complain about that! If it's not directly related, I would leave this change out

Copy link
Contributor

@imtayadeway imtayadeway left a comment

Choose a reason for hiding this comment

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

Change LGTM. I'm not sure if it was impossible to git cherry-pick any of the upstream revisions so that it directly relates back to that (noting what conflicts you had) - that might have been better. But I'm good with this as far as the code is concerned. Thanks @jntullo ! 🎈

@simaishi simaishi merged commit fee815e into ManageIQ:euwe Jul 7, 2017
@simaishi simaishi added this to the Sprint 64 Ending Jul 10, 2017 milestone Jul 7, 2017
@chrisarcand chrisarcand deleted the euwe_correct_field_names branch November 28, 2017 19:28
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.

6 participants