-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"--operationId" still includes service name #133
Comments
@maxoosterveen |
This is blocking for me on migrating over - any pointers on where to start looking? |
@maxoosterveen @JoeHillyard npm i -D @7nohe/openapi-react-query-codegen@0.0.0-ef2157e65a33494afbc157e7e72b47353a84e49a If there are no issues, I will merge this PR and release it. |
Hmm i don't seem to be having any luck - service name is still coming through |
Same - still getting service names when using version |
We have adopted Flat Services from version 2 to support tree-shaking, and as a result, service names have been deprecated. |
Describe the bug
When running the generator command with the option
--operationId
still includes the service names in the hooksTo Reproduce
Steps to reproduce the behavior:
pnpm exec openapi-rq -i ./internal.json --operationId
OpenAPI spec file
If possible, please upload the OpenAPI spec file.
Expected behavior
A clear and concise description of what you expected to happen.
Instead of having the service name in the function hook, I would like it to only use the operation id.
useServiceNameOperationId > useOperationId
Screenshots
If applicable, add screenshots or logs to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: