fix: multiple formats for custom "api_doc" route example

[phansys]

Without the _format option, the resulting route is not able to expose other paths like /api_documentation.jsonopenapi.

[alanpoulain]

Are these necessary as well?

[phansys]

I think so. Without the methods definition, the route will accept any HTTP verb.

This condition was added in version 3.3.7.

The default format is required for the routing to match the /api_documentation.{_format} pattern. Otherwise, a request to the /api_documentation path results in 404, as the pseudo-extension (.html in this case) is missing.

[soyuka]

shouldn't we merge this on a 3.x branch?

[phansys]

shouldn't we merge this on a 3.x branch?

I've chosen the 2.7 branch, as this branch is the older one where the route is defined. The version 3.3.7 was the first one introducing these improvements / fixes in the default route definition, although I guess this situation is not a blocker to provide these changes from the branch where the route was introduced.

Please, let me know if you agree. Otherwise, I can update the target branch to 3.7 based on your answer.
Thank you.

[vinceAmstoutz]

shouldn't we merge this on a 3.x branch?

I've chosen the 2.7 branch, as this branch is the older one where the route is defined. The version 3.3.7 was the first one introducing these improvements / fixes in the default route definition, although I guess this situation is not a blocker to provide these changes from the branch where the route was introduced.

Please, let me know if you agree. Otherwise, I can update the target branch to 3.7 based on your answer. Thank you.

@phansys Yes, you're right but we currently support >= 3.3 branches. Please target the 3.4 branch for this one. For more details check out our Maintenance documentation.

[phansys]

The target branch was changed to 3.4. Thanks.