Feature request: abstract states

While trying to build a custom framework around router5, heavily utilizing the implementation of nested states, I’ve found myself in need of abstract states - state that has optional path and can’t be navigated to, but trigger relevant events and can be used in custom pipeline.

For instance - I’ve got two layout pages public and private. These would both trigger their events when transitioning from one child state to another (or just be used in custom pipeline), but there would be no way to navigate to them directly.

.addAbstractNode('public')                      // abstract state without url
.addAbstractNode('public.account', '/account')  // abstract state with url (for inheritance to child states)
.addNode('public.account.signIn', '/sign-in')   // normal state

.addAbstractNode('private')                     // abstract state without url
.addNode('private.home', '/')                   // normal state

Such instance would only allow going to / and /account/sign-in.

[troch]

I think I will split that work into two features:

• abstract states (states which cannot be activated, but children can)
• path-less states (states without a defined path)

an abstract state can be path-less or not. A path-less state can be abstract or not.

[troch]

@LeonardoGentile worked as expected for you?