-
Notifications
You must be signed in to change notification settings - Fork 357
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
Enablement and Visibility expression UI for custom buttons #1792
Conversation
@@ -47,7 +47,7 @@ def exp_button | |||
end | |||
|
|||
if flash_errors? | |||
javascript_flash(:flash_div_id => 'adv_search_flash') | |||
javascript_flash |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
- Go to Compute --> Infra --> VM --> actually select the VMs accordion
- Open the advanced search (arrow next to search field)
- Add in a field, but do not select what to do with that field (create an un-complete expression)
- 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.
There was a problem hiding this 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,... )
418be20
to
9cea56d
Compare
Review notice: the UI is just ugly. We need to fix that in some future PRs. Ping @epwinchell ? Please? |
@martinpovolny I know you were fixing some bugs, let us know when this is ready. |
This pull request is not mergeable. Please rebase and repush. |
Add visibility filtering for custom buttons
d3dd52a
to
a6bdb57
Compare
Checked commits martinpovolny/manageiq-ui-classic@6c3ac3b~...a6bdb57 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
The bug I was fixing: (c-n-ped from above): Yeah so this actually breaks the expression editor inside the advanced search.
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. |
@martinpovolny agreed |
Tested in UI other than styling issues, looks good. |
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.