Details
Description
This is an umbrella issue for several module-specific issues to come.
We use react-router to get into the settings area:
http://folio-testing.aws.indexdata.com/settings
And into individual modules' settings areas:
http://folio-testing.aws.indexdata.com/settings/users
And into specific pages of a module's settings:
http://folio-testing.aws.indexdata.com/settings/users/perms
But once we're in the individual pages, most of them use local state to navigate between specific objects that are being maintained. For example, in the permission-set editor, the same URL (shown above) is used for editing Jakub's Set or Untitled Permission Set or any other set.
We should use proper routing all the way down, so that we'd have URLs like
http://folio-testing.aws.indexdata.com/settings/users/perms/Jakub's+set
Related to this, I worry that we are starting to proliferate settings pages with very similar code. We should look at whether we can abstract out a skeleton that can be customised.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
STCOM-92 Copy <EntrySelector> into stripes-components
-
- Closed
-
-
UICIRC-26 Rewire the Loan Policies editor to use <EntrySelector> from stripes-components
-
- Closed
-
-
UIU-276 Rewire the Permission Set editor to use <EntrySelector> from stripes-components
-
- Closed
-
- relates to
-
UICIRC-15 Create/Edit Loan Policy Form in Full-Page Overlay
-
- Closed
-
-
UIU-231 Create/Edit Permission Set Form in Full-Page Overlay
-
- Closed
-
-
STSMACOM-6 Move <AuthorityList> into stripes-smart-components
-
- Closed
-
-
UIU-79 CRUD Address Types
-
- Closed
-