fix(msw): changed naming convention for response mock functions to avoid function name conflicts

[soartec-lab]

Status

READY

Description

fix #1106

This issue is occur when the path name and operationId are the same. So a rare case because operationId is usually used like addXX or getXXX, but i will fix it because it causes unintended problems for users.

orval gets the mock name from title, which is the same naming convention as the response mock.

response mock function naming

`get${pascal(operationId)}Mock`;

mock function naming

`get${pascal(title)}Mock`,

Ref: https://github.com/anymaniax/orval/blob/master/packages/orval/src/client.ts#L172

Therefore, I changed the response mock function name.
It's a breaking change, but out of all my ideas, I decided to do this because it has the least impact.

Related PRs

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

1. specify mock: true in orval.config.js
2. execute orval
3. check the name change in the generated mock function