Method Names postfixed with Numbers about openapi-typescript-codegen HOT 7 OPEN

@andreujuanc the pull request also changes the replacement pattern so I'd expect a different result for their use case, but will need them to try it since I can't see their OpenAPI spec

from openapi-typescript-codegen.

I think it's because both are under the same Tag? I'm currently looking for a way to set an operationId on my spec to set the method name to something better.

EDIT: See #314

from openapi-typescript-codegen.

@donkey-donkey @andreujuanc can you try our fork if that works as you'd expect?

from openapi-typescript-codegen.

Can't at the moment. But just for the record, the current lib will use the operationId for naming, so that should be good enough if you have control over the spec.

EDIT: Gave it a star. Will check as soon as I can.

from openapi-typescript-codegen.

As @mrlubos pointed out, this might be resolved by #2043.

from openapi-typescript-codegen.

You'll want to set the new --useOperationId flag to false to try the alternative method name generator. It's available in the latest release, please let us know whether it worked if you try it

from openapi-typescript-codegen.

I think OP was asking "why the number suffix", and the answer is because I believe there is no operationId on their spec, and the paths are both on the same Tags. Ignoring the operationId would yield no change to the generated methods.

from openapi-typescript-codegen.