MSTR-228: Allow app custom routing

[guillegr123]

This change allows to redirect to a registered app, if the first 2 parts of the hash route match a valid app, on load/re-load. For example:

• apps/callcenter/queues/abc123/members redirects to apps/callcenter
• apps/cluster/tasks redirects to apps/cluster

This enables Monster UI to load, reload or redirect to apps that use their own sub-routing system.

Normal routes (app/{appName}) and invalid routes should work as usual.

[joristirado]

Are some changes in this PR missing maybe?

monster.routing#hasMatch does not take any arguments: it only checks the current hash against apps/{appName}:?query.

[guillegr123]

Sorry @azefiel , you are absolutely right, I forgot to commit the change for monster.routing#hasMatch 😅

It should be up now. Thanks for the heads up.

[joristirado]

Not sure this is the best way to go about this, as we have a dedicated library to abstract routing concerns.

Adding a new route pattern seems like a straightforward solution in this case.

It looks like crossroads's route registration facility has a flexible enough pattern matching mechanism to meet our needs (so called "rest segments" could be what we need here).

Happy to jump in a huddle any time to discuss this further if needed.

[guillegr123]

Hi @azefiel, I tried using the rest fragments, but it seems that Crossroads.js does not support having both an optional rest fragment and an optional query capturing group. So I ended up using a regular expression instead, and exposing the parseQueryString() function at monster.util, to convert the extracted query string into an object as Crossroads.js used to do.

[joristirado]

Last nitpicking, just want to make sure this code is as understandable as possible for our future self 😅