routesMap: generic regex takes precedence before more specific route

I may have missed something, but at least the question is very specific. I have following route map:

SPECIFIC: {
  path: '/specific'
},
GENERIC: {
  path: '/:generic+',
}

The thing is, that I cannot really access SPECIFIC route through the browser. The route is being resolved correctly while using redux-first-router-link + to prop + action, however when I refresh the page (or just enter the URL from outside of the app), I get the screen/content from the GENERIC route.

So the question is, is there an option to make more specific routes take precedence before the more generic ones?

I kinda realise that the routes design here may not be the smartest, and I probably should have some constant prefix before the GENERIC route, was just wondering if its somehow possible.

Already looked here: https://github.com/faceyspacey/redux-first-router/issues/83#issuecomment-327703226 but haven’t really found any answer.

[ScriptedAlchemy]

Hmm, this is a good point. I do like the idea of ranking.

[ScriptedAlchemy]

Will open this issue again on a new repo. RFR will be entering LTS and Rudy will be where new features are added. Ill update the readmes once i move it off a branch on this repo