I use Angular UI Router, I manage them by defining one route/state/control per file. And group states together using
index.js so I can package them in individual folders.
In addition I have 3 top level states
At least 2 abstract states
- authenticated (which could be authenticated-admin, autheneticated-user, etc.)
And each CRUDL type construct would have their own top level state followed by their substates
- index.js (to group it together)
Once you have the core domain object work done, you add “business” routes to make it easier for people to use your product by going through a business transaction flow such as creating a social work case (search for duplicate -> register person -> capture case header information -> activate case) each of those being their own route. So you can predict the number of states that need to be created. Useful for estimations.