asClass option support for @tanstack/react-query (an analog of @hey-api/sdk)

[maksim-optifino]

Hello

We are planning to start use @tanstack/react-query for our project. Got naming problem with generated functions - they duplicates because we use the same operationId for similar functions in different services. asClass option from @hey-api/sdk allows us to have the same names for functions (they are wrapped in different classes).

Are you planning to add some way to handle such situation without operationId change in input file? (maybe react on asClass option from @hey-api/sdk, or separate configuration property or function in @tanstack/react-query)

[mrlubos]

@maksim-optifino is bundle size not a concern? How would your generated output ideally look like?

[maksim-optifino]

Bundle size is not main concern for now (but it may become if such approach will have heavy impact)

Ideally follow sdk pattern

for example what we have in sdk:
AdminClientManagementService
--- createClientProfile

AgentClientManagementService
--- createClientProfile

so in react-query
AdminClientManagementService
--- createClientProfileQueryKey
--- createClientProfileOptions

AgentClientManagementService
--- createClientProfileQueryKey
--- createClientProfileOptions