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

Enablement and Visibility expression UI for custom buttons #1792

Conversation

martinpovolny
Copy link
Member

Rebase of #1739

I had to merge @skateman's #1685 because the model changes are already in and this broke @lgalis 's PR #1739 that I am reviewing.

@@ -47,7 +47,7 @@ def exp_button
end

if flash_errors?
javascript_flash(:flash_div_id => 'adv_search_flash')
javascript_flash
Copy link
Member Author

@martinpovolny martinpovolny Jul 31, 2017

Choose a reason for hiding this comment

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

$ grep -r adv_search_flash app/
app/views/layouts/_adv_search_body.html.haml:    = render :partial => 'layouts/flash_msg', :locals => {:flash_div_id => 'adv_search_flash'}
app/views/layouts/_adv_search_body.html.haml:      = render :partial => 'layouts/flash_msg', :locals => {:flash_div_id => 'adv_search_flash'}

Does this change break the other places where we use the expression editor?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah so this actually breaks the expression editor inside the advanced search.

  1. Go to Compute --> Infra --> VM --> actually select the VMs accordion
  2. Open the advanced search (arrow next to search field)
  3. Add in a field, but do not select what to do with that field (create an un-complete expression)
  4. press the "✓" symbol

A flash message should appear in the expresion editor, but it is actually sent to the flash_msg_div below the opened modal.

@lpichler
Copy link
Contributor

I tested it and expression and display text are stored correctly 👍

Only maybe there is some issue with styling (I think that there is the bigger font but I am not sure):

screen shot 2017-07-31 at 16 10 53

Copy link
Contributor

@lpichler lpichler left a comment

Choose a reason for hiding this comment

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

tested 👍 saving the form with various values (empty,... )

@martinpovolny martinpovolny force-pushed the pull-request-lgalis-add_expression_support_to_custom_button_editor branch from 418be20 to 9cea56d Compare August 1, 2017 09:15
@ManageIQ ManageIQ deleted a comment from miq-bot Aug 1, 2017
@martinpovolny
Copy link
Member Author

Review notice: the UI is just ugly. We need to fix that in some future PRs. Ping @epwinchell ? Please?

@dclarizio
Copy link

@martinpovolny I know you were fixing some bugs, let us know when this is ready.

@miq-bot
Copy link
Member

miq-bot commented Aug 2, 2017

This pull request is not mergeable. Please rebase and repush.

@martinpovolny martinpovolny force-pushed the pull-request-lgalis-add_expression_support_to_custom_button_editor branch from d3dd52a to a6bdb57 Compare August 2, 2017 15:10
@miq-bot
Copy link
Member

miq-bot commented Aug 2, 2017

Checked commits martinpovolny/manageiq-ui-classic@6c3ac3b~...a6bdb57 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
16 files checked, 0 offenses detected
Everything looks fine. 🍰

@martinpovolny
Copy link
Member Author

The bug I was fixing: (c-n-ped from above):

Yeah so this actually breaks the expression editor inside the advanced search.

  1. Go to Compute --> Infra --> VM --> actually select the VMs accordion
  2. Open the advanced search (arrow next to search field)
  3. Add in a field, but do not select what to do with that field (create an un-complete expression)
  4. press the "✓" symbol

A flash message should appear in the expresion editor, but it is actually sent to the flash_msg_div below the opened modal.

962b778 should fix that. Please, test and merge.

The form design is pretty ugly, but we can surely work on that in a separate PR.

@epwinchell
Copy link
Contributor

The form design is pretty ugly, but we can surely work on that in a separate PR.

@martinpovolny agreed

@h-kataria
Copy link
Contributor

Tested in UI other than styling issues, looks good.

@h-kataria h-kataria added this to the Sprint 66 Ending Aug 7, 2017 milestone Aug 2, 2017
@h-kataria h-kataria merged commit 67768fe into ManageIQ:master Aug 2, 2017
@martinpovolny martinpovolny deleted the pull-request-lgalis-add_expression_support_to_custom_button_editor branch November 28, 2017 18:46
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.

7 participants