You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are a few mock filters that use API driven mechanism to search/etc. These are old implementations and have been updated with some modern work on newer Django filters.
These are the filters that I'm describing:
For example, on the organization listing view, the dropdown is a simple filter object and is displayed as normal from the filter menu:
These last two filters can be updated to match, which would also remove some of the bad UX around this filter UI.
Places this pattern was used:
Project listing view
Project version listing view
Build listing view
The text was updated successfully, but these errors were encountered:
It's working great I think. This deletes a lot of JS code from our dashboard, moving the code to django-filter Python logic, which I think is another win. I didn't go as far as to use web components for the client side logic, as the majority of this is still application template driven.
But for now, the filters feel a bit easier to use:
This drops the custom API driven filters and relies on application
FilterSet instances instead, matching the rest of the filter fields.
Because of this, we are able to delete much of the JS and API logic from
the dashboard side.
- Fixes#343
- Closes#250
- Requires changes on our application filters
* Listing filter UX changes
This drops the custom API driven filters and relies on application
FilterSet instances instead, matching the rest of the filter fields.
Because of this, we are able to delete much of the JS and API logic from
the dashboard side.
- Fixes#343
- Closes#250
- Requires changes on our application filters
* Fix docs
Currently, there are a few mock filters that use API driven mechanism to search/etc. These are old implementations and have been updated with some modern work on newer Django filters.
These are the filters that I'm describing:
For example, on the organization listing view, the dropdown is a simple filter object and is displayed as normal from the filter menu:
These last two filters can be updated to match, which would also remove some of the bad UX around this filter UI.
Places this pattern was used:
The text was updated successfully, but these errors were encountered: