fix(useNamedParameters): use operationName instead of operationId

[Marcel-G]

Status

READY

Description

This feature was using operationId to construct the PathParameters name. For consistency, it would be better to use operationName as it can be mapped to something by users.

Related PRs

List related PRs against other branches:

branch	PR
other_pr_production	link
other_pr_master	link

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

Outline the steps to test or reproduce the PR here.

> git pull --prune
> git checkout <branch>
> grunt jasmine

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @anymaniax on Vercel.

@anymaniax first needs to authorize it.

[anymaniax]

Hello @Marcel-G seems good but could be a breaking change in some cases no?

[Marcel-G]

Hello @Marcel-G seems good but could be a breaking change in some cases no?

Technically yes, since the path parameter types are public and would effect consumers who:

• Are already using useNamedParameters and
• Have operations named with operationId or custom naming override and
• Are directly importing the Path parameters model type in their projects

[anymaniax]

@Marcel-G should be a really little number of ppl tho no?

[Marcel-G]

@Marcel-G should be a really little number of ppl tho no?

Yes very few I imagine

[anymaniax]

@Marcel-G I don't know if you are often on discord but if you could be discuss there with the other maintainers would be great