-
Notifications
You must be signed in to change notification settings - Fork 15
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
Task/wg 375 recon portal UI changes #1435
Task/wg 375 recon portal UI changes #1435
Conversation
- Removes external dataset header and toggle and associated styles - Adds debounced search button for each row - Changes order of Clear and Hide buttons, adds filter to the wording in the button - Adds checkbox to hide and add Recon Portal data
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.
LGTM! Great work.
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.
LGTM! Just added a couple non blocking comments
<div class="filter-button-row"> | ||
<button class="btn btn-xs btn-default filter-btn" ng-click="vm.show_filter_options=false"> Hide Filters </button> | ||
<button class="btn btn-xs btn-default filter-btn" ng-click="vm.clear_filters()"> Clear Filters </button> | ||
<button class="btn btn-xs btn-info filter-btn" ng-click="vm.debouncedSearch()" ng-disabled="(!vm.data_source && !vm.ot_data_source)"> Search </button> |
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.
Since there is a proper search button now we don't have to worry about debouncing the search so we should be able to use search() directly
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.
The search in the sidebar still uses this function. Should that change to the search method instead as well? I think the auto-updating in that area makes sense but we will probably have to defer to CMD on that UI anyway. I can remove it and implement the search the same way as the filter though if you think that would be better.
handles this through the service - Search button uses search method on click rather than debouncing
Overview:
Requested UI changes from Tracy before 4Kitchens and CMD design review
PR Status:
Related Jira tickets:
Summary of Changes:
to the wording in the button
Testing Steps:
UI Photos:
Main screen with filters showing
No dataset match for filters
Notes: