Custom fetch options are stripped from the request. Next.js cache doesn't work properly.

[petercsaki]

Description

Openapi-fetch uses a request object for its fetch.

openapi-typescript/packages/openapi-fetch/src/index.js

Line 101 in 9c277fb

let response = await fetch(request);

The request object created by openapi-fetch strips away non standard fetch options, i.e. how Next.js passes its cache related params:

{ next: { revalidate: 3600 } }

More info on Next.js fetching data + caching

Reproduction

Try to pass next cache params in https://github.com/drwpow/openapi-typescript/blob/main/packages/openapi-fetch/examples/nextjs/app/page.tsx
It won't change its behaviour, it always falls back to defaults, because the non standard ones are stripped away.

I've tried

I changed this line

openapi-typescript/packages/openapi-fetch/src/index.js

Line 101 in 9c277fb

let response = await fetch(request);

to

let response = await fetch(request, requestInit);

and it works, but I don't know if it would cause other problems.

[drwpow]

Ah, hm. I was somewhat afraid this would happen, and did see it come up in one other test failure, but had thought it was fixed.

Would gladly welcome any PRs for this! This should be a fairly-straightforward issue to write a failing test for, and find a fix.

[petercsaki]

PR created.

[JE-lee]

For the workaround, this could be ok as well as the cache mechanism, regardless a little wired.

  const res = await client.GET("/api/v1/space", {
    fetch: (request: unknown) => {
      return fetch(request as Request, { next: { revalidate: 40 } } )
    }
  })

I have tested it in Next.js 14

[FreeAoi]

Hi, a pull request fixing this was merged #1653 recently