[regression][policy, no patch] Route parameters must be able to be provided along with route names

One concern that was raised by timplunkett is that we cannot provide dynamic parameter values. Within the context of a statically defined route name (just we defined static URL paths in Drupal 7) this is true. This is, however, no regression. Example: just like *.info files in D7 provided a configure route path with the (static) placeholder values filled in, in D8 that value would be a route name, with an additional array of static route parameters. Instead of entering them into the URL directly, we provide a map, but the values in questions have been and will remain static, as long as the context is static as well.

This hasn't manifested itself as a regression in Drupal core (yet), but it has in contrib.

The regression is that if route parameters are unsupported, we can no longer link to URL paths with placeholders/wildcards/parameters.

Do you mean #2154743: Support route parameters for *.config_translation.yml files' base_route_name properties?

Regardless of any Configuration Translation issues, what are your thoughts on this issue in general?

Can I ask why you think this does not to be done everywhere? The way I see it, anything that needs to do something with a route has no right to impose any limitations on that route.

Bump.