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
Add filter by asset type
I have many assets that I can see from my account. Filter by name is good but a filter by asset type would help.
I think they should be cumulative filters, only show asset that passed all filters.
I would like to be able to filter by asset type.
I am willing to try to add this to the UI but need a pointer to where to start.
Show asset type at/near the top of asset page
I also want to the individual asset page to show asset type at/near the top.
Names are not always descriptive
I should not have to open the asset edit to see this information
Not a big issues but I am curious on your feedback
The text was updated successfully, but these errors were encountered:
The API endpoint should show nicely how we add filters, and how we use MarshMallow to define API parameters (such as your new filter).
Yes, go ahead and add that information if you think it is useful.
In the single asset view (/assets/ID), we also use the API, but from within the backend code itself. FYI: It's been leading to code that sometimes gives more trouble than it's worth, so we are slowly transitioning to the more direct JS->API way of working in the frontend. However, in this case, you get the asset type already worked out (as the asset API would only give you the asset type ID - I believe here you already get the name and it should be easy work).
I have many assets that I can see from my account. Filter by name is good but a filter by asset type would help.
I think they should be cumulative filters, only show asset that passed all filters.
I would like to be able to filter by asset type.
I am willing to try to add this to the UI but need a pointer to where to start.
I also want to the individual asset page to show asset type at/near the top.
The text was updated successfully, but these errors were encountered: