Can't use `@pinia/colada` plugin with `@hey-api/client-nuxt`

[RihanArfan]

Description

When using the Nuxt client, then trying to use the @pinia/colada plugin, the generated Pinia queries doesn't use the ofetch/Nuxt client SDK syntax.

Here it's destructuring data from getV1Items but the ofetch client returns data directly

Reproducible example or configuration

https://github.com/RihanArfan/hey-api-nuxt-pinia-repro
pnpm i
pnpm dev

OpenAPI specification (optional)

https://raw.githubusercontent.com/sysadminsmedia/homebox/refs/heads/main/backend/app/api/static/docs/swagger.json

System information (optional)

No response

[dosubot]

Hi @RihanArfan! I'm Dosu and I’m helping the openapi-ts team.

The issue comes from a mismatch between how @pinia/colada expects to destructure the response (e.g., expecting an object with a data property) and how the Nuxt client SDK (@hey-api/client-nuxt, which uses ofetch) actually returns the response (the data is returned directly, not wrapped in an object) [source].

There isn’t any official documentation or built-in option addressing this specific compatibility issue. However, since the Nuxt client SDK supports custom $fetch implementations and interceptors, you could adapt the response shape before it reaches your Pinia store. For example, you could wrap the direct response in an object with a data property using a custom $fetch or a response interceptor [source].

This way, the destructuring in your Pinia queries will work as expected. If you need a code example for this workaround, let me know!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[brolnickij]

you can use this config

import { defineConfig } from '@hey-api/openapi-ts'

export default defineConfig({
  input: 'https://raw.githubusercontent.com/swagger-api/swagger-petstore/master/src/main/resources/openapi.yaml',
  output: './src/client',
  plugins: [
    '@hey-api/sdk',
    {
      name: '@pinia/colada',
      queryOptions: true,
      mutationOptions: true
    },
    '@hey-api/typescript'
  ]
})

in my test environment, it works without issues