You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a route is defined as path: '/exports/news.{!_format}', we should force _format be defined in "defaults" and the generator should generate URLs with that default when none is provided (should work with any parameter of course.)
…s using eg "/exports/news.{!_format}" (zavulon)
This PR was squashed before being merged into the 4.3-dev branch (closes#29599).
Discussion
----------
[Routing] Allow force-generation of trailing parameters using eg "/exports/news.{!_format}"
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #29593
| License | MIT
When a route is defined as path: `/exports/news.{!_format}`, we should force `_format` be defined in `defaults` and the generator should generate URLs with that default when none is provided (should work with any parameter of course).
Commits
-------
9fab3d6 [Routing] Allow force-generation of trailing parameters using eg \"/exports/news.{!_format}\"
When a route is defined as
path: '/exports/news.{!_format}'
, we should force_format
be defined in "defaults" and the generator should generate URLs with that default when none is provided (should work with any parameter of course.)Better described in #28633 (comment)
The text was updated successfully, but these errors were encountered: