Closed CHE1RON closed 1 month ago
services.gen.ts
is a file generated on the @hey-api/openapi-ts
side, so it falls outside the scope of this library.
This issue can likely be avoided by using operationId.
@7nohe Thanks for letting me know 🙏
I guess I'll open an issue upstream then. How exactly does operationId
work? From the docs it seems to be a flag, but its default is true
.. ?
@CHE1RON Yes, the default is true. Therefore, all you need to do is make each operationId unique.
"paths": {
"/api/v1/boards/export": {
"get": {
"tags": ["boards"],
"summary": "Returns an export of a collection of boards.",
"operationId": "boards-export",
"/api/v1/documents/{file}/export": {
"get": {
"tags": ["documents"],
"summary": "Exports the document as a PDF with annotations included.",
"operationId": "documents-export",
Describe the bug When having endpoints of the same name, eg
tags/{tag}/export
andlabels/{label}/export
, only one data type is generated (hereExportData
) for all services, which is correct for the first, but wrong for all subsequent services.To Reproduce
tags/{tag}/export
andlabels/{label}/export
services.gen.ts
OpenAPI spec file routes.json
Expected behavior Data types free of conflicts, eg
ExportData
,ExportData1
, etcScreenshots If applicable, add screenshots or logs to help explain your problem.