Issue Task New Orphaned

#91702Evaluate possibility for optional route parts

Oliver Hader 06/23/20, 23:53 updated 08/02/23, 13:05

Description

The following would lead to URL parameters like &value=abc&optional=

routerPath: '{value}/{optional}'
defaults:
  optional: ''

The desired behavior would be to not expose the URL parameter optional at all, thus only having &value=abc.

routerPath: '{value}/{optional}'
defaults:
  optional: null

This example is untested – in case it works already, cool.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[TASK] Evaluate possibility for optional route parts Resolves: #91702 Releases: main