Optional URL Parameter Compatibility

[siddiqar]

Laravel provides optional parameters in routes by appending a " ? " at the end of the parameter name. However, the generated collection does not account for this, resulting in parameters like example.test/{param?}. Ideally, these should still be converted into URL parameters, with optionality preserved or handled appropriately.

For example:

Route definition: example.test/{param?}
Expected conversion: example.test/:param (with recognition of the parameter being optional)
This behavior needs to be addressed to ensure compatibility with Laravel's route syntax and proper handling of optional parameters in the generated output.

[tomirons]

@siddiqar can you please provide an example route definition that will help us replicate what you're seeing?