fix: * param renamed to wildcard

[casantosmu]

This plugin transforms the route "/example/*" into "/example/{wildcard}". Therefore, the schema for a route with a wildcard should be defined as follows:

fastify.get(
  "/example/*",
  {
    schema: {
      params: {
        wildcard: { type: "string" },
      },
    },
  },
  (request, reply) => {
    const path = request.params["*"];
    reply.send(path);
  }
);

This pull request allows defining the schema for a route with a wildcard as expected:

fastify.get(
  "/example/*",
  {
    schema: {
      params: {
        "*": { type: "string" },
      },
    },
  },
  (request, reply) => {
    const path = request.params["*"];
    reply.send(path);
  }
);

This resolves the issue discussed in this GitHub issue.

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[casantosmu]

As mentioned in the issue, there was another potential solution: when transforming the Fastify schema to OpenAPI, updating the parameter "*" to "wildcard" could have been an option. Similar to the transformation applied to the URL. However, I believe it is simpler for everyone to maintain consistency by preserving the parameter names in the path rather than modifying them.

[mcollina]

lgtm

[mcollina]

looking at the change, I don't think it's semver-major.

[climba03003]

looking at the change, I don't think it's semver-major.

Yes, changing the displayed pathname doesn't cause any problem.
It just not good for identify what it intended to do.

Note: The same thing would happen on unnamed RegExp param.