feat: Attach fetch response to SWR data/error

[Tommos0]

Changes

It is useful to have the original fetch response available in the hook result. For instance to distinguish the HTTP status code in case of an error. Since SWR only returns error / data properties, this provides an escape hatch to be able to access to original fetch response, as returned by the openapi-fetch client.

This will probably fail for JSON bodies that parse to primitives (null/string).

#2238

Checklist

I was unable to run the test suite, making it hard to add / update unit tests for me.

[netlify]

👷 Deploy request for openapi-ts accepted.

Name	Link
🔨 Latest commit	deef3fe
🔍 Latest deploy log	https://app.netlify.com/projects/openapi-ts/deploys/67f4ddd2015f990007f9c55c

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4070c42

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[drwpow]

Thanks! Not opposed to this fix itself, but we will need a test to make sure this doesn’t regress in the future.

Could you describe the error you were seeing when running the test suite? Are you on the current LTS Node version (22) and did you follow the instructions in CONTRIBUTING.md?

[drwpow]

Just a heads up: the repo has since been moved here, so this PR will need to be moved to changeset-release/main. Please feel free to repoen there! (But the test requirements will be the same)