DynamicRouteValueTransformer - Continues to search for routes

[joestant]

I have implimented the DynamicRouteValueTransformer for CMS pages within VS2019 Preview and .Net 5.0.0 4.20257.10.

Some CMS pages are suffixed, such as /reviews/ or /job-adverts/ etc.

To get around this i've implemented two MapDynamicContollerRoutes

endpoints.MapDynamicControllerRoute<CmsRequestTransformer>("/{companyname}/{action:regex(^(reviews|job-adverts)$)}/{id?}");
endpoints.MapDynamicControllerRoute<CmsRequestTransformer>("/{**slug}");

However, when the first route is found it will continue to the next...
The {**slug} won't find it as these CMS pages - in theory don't exist in the CMS. (I could inject them in though, but would multiply many routes within the cache. the companyname could be anything and be added or removed at any time).

Is there anway to check if a route has already been found or prevent the second route firing? This is doing another look up, hitting my cache. I'd like to prevent this by a simple found check. I have looked far and wide to no avail.

Background -
To prevent the {**slug} issue I have used the known work around, ActionResult route filters. Which is working. The only routing I have within UseEndpoints is my DynamicRouteValueTransformer.
Why am I doing this? I'm migrating an application from MVC 5 .Net 4.7.2 that used
var routes = RouteTable.Routes; using (routes.GetWriteLock()) {..... this was used to update the CMS after the website is compiled.

DynamicRouteValueTransformer seems the best option for .net 5. I'm handling many routes with no hints such as /blogs or /article, and if they do have a category, the category is from the CMS.

[mkArtakMSFT]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we will planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[DrSoops]

Adding my personal use case (which I could see being a generic use case as it grows) to this topic.

In my case I have a few routes that need to be handled differently but have the same url structure.
Routing patterns

endpoints.MapDynamicControllerRoute<HealthTransformer>("/{controller}/{area}/Health");
endpoints.MapDynamicControllerRoute<GenericTransformer>("/{controller}/{area}/{action}");

Sample requests

Controller/Foo/Health
Controller/Bar/Action

In this case anything that ends with Health should be treated as a Health check and will have a generic implementation where the latter will have extra logic to route to the correct controller and action.
It would be very beneficial to have the same built in routing precedence that already exists for non-dynamic routing.
Currently as @joestant mentioned both DynamicRouteValueTransformer are being executed.