Allow Regex and Array in request mapping decorator

[abouroubi]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[X ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

When we decorate a controller function with the Post, Get, ... decorators, the param must be a string, but as the documentation of Express JS (https://expressjs.com/en/4x/api.html#path-examples) we can use Regex or array of strings, to match with multiple paths.

Is it possible to change it to allow this two types ?

Expected behavior

The possibility to use regex and arrays as params of a request mapping decorator.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Adding aliases for a route, for example for backward compatibility.

Environment

Nest version: 5.4.1

For Tooling issues:

• Node version: XX
• Platform:

Others:

[abouroubi]

I checked the fastify documentation, and it seems like they don't support the array version out of the box, so if we want to support this in NestJS, we will need to find a workaround for providers other than express.

[elyesbenabdelkader]

Also I think fastify, unlike express, does not support RegExp objects.

[marcus-sa]

Each server adapter should just validate whether or not regex etc is a valid option to use.

[kamilmysliwiec]

PR merged and published as 5.7.0

[JohannesHoppe]

I would argue that this issue is only half done. Yes, now you can use an array of strings, but the OP also asked for a regex.

That would be very important for me so that we can migrate from an existing express.js solution.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.