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
As a user I'd like to be able to collapse screen-names / routes in the left side-menu of the Design builder. Similar to the component trees, this would allow for quicker screen navigation with apps that have many routes.
Role-based should be the default (as the current sorting algo does) but sorting by name would be a plus.
A filter field would be awesome, allowing quick access to routes via an (externally) documented route schema, e.g. showing all routes that contain 'create' or all routes containing
'/v1/' or 'individual' or ':entity_id' etc..
This would add better usability as the current implementation is quickly overwhelming with many screens despite a clear route nomenclature.
The ability to filter screens by route paths also helps focusing on the task at hand and implement changes more easily.
Would make a great product even better, I think. What's your take on this?
Thanks and sorry if this has been asked before, search-fu didn't show any relevant hits.
The text was updated successfully, but these errors were encountered:
Collapsible / tree-view for screens
As a user I'd like to be able to collapse screen-names / routes in the left side-menu of the Design builder. Similar to the component trees, this would allow for quicker screen navigation with apps that have many routes.
Role-based should be the default (as the current sorting algo does) but sorting by name would be a plus.
A filter field would be awesome, allowing quick access to routes via an (externally) documented route schema, e.g. showing all routes that contain 'create' or all routes containing
'/v1/' or 'individual' or ':entity_id' etc..
This would add better usability as the current implementation is quickly overwhelming with many screens despite a clear route nomenclature.
The ability to filter screens by route paths also helps focusing on the task at hand and implement changes more easily.
Would make a great product even better, I think. What's your take on this?
Thanks and sorry if this has been asked before, search-fu didn't show any relevant hits.
The text was updated successfully, but these errors were encountered: