Skip to content

Home

Jump to bottom
Rene Dohmen edited this page Mar 28, 2023 · 2 revisions

Welcome to the orchestrator-ui wiki!

We will document some design decisions here.

This is an example of the new subscription page:

image

Notes:

Some changes regarding this design:

  • no crumble path
  • submenu's and tabs will be used. The Tabs use a short name
  • pages under subscriptions will highlight "Subscriptions" and expand the menu
  • if a page under a main menu is selected and it has a sub menu item: the main and submenu item will be selected
  • pages that have a tab or an active menu item: wil not show an header (so a detail page will show a header, a subscription table not)

Some notes regarding persisting table state in the URL:

  • only pageSize and visibleColumns will be stored in local storage
  • empty filter will not be needed in the URL (e.g. no &filter= at the end of the URL for an empty filter
  • visible columns are stored by giving the columns a number. E.g. store only the visible column indexes
  • the default sort can also be omitted: as you can't override it from local storage
  • the size can be omitted if it's not overriden in local storage
  • the visible columns can be omitted if it's not overriden in local storage
  • we store the table settings for each "top" table. So there is one local storage key for subscriptions and one for processes.

The vision behind this logic: we want clean URL's when the user didn't override anything, but we also want URLS that can be shared with others and will result in exactly the same table. The vision behind this logic: we want clean URL's when the user didn't override anything, but we also want URLS that can be shared with others and will result in exactly the same table.

Clone this wiki locally