RFC: Augment error extensions type

[musjj]

Summary

GraphQL servers can extend the error type with extensions. An example from this repo:

urql/examples/with-refresh-auth/src/client.js

Lines 32 to 36 in 7f9cad5

	didAuthError(error) {
	return error.graphQLErrors.some(
	e => e.extensions?.code === 'UNAUTHORIZED'
	);
	},

Depending on the server implementation, the shape of the extensions may be uniform across all error responses. In that case, it would be helpful if the client can augment the default Record<string, any> with the actual expected type.

Proposed Solution

Augmenting types can look something like this:

declare module "@urql/core" {
  interface Extensions {
    code: "FORBIDDEN" | "INTERNAL_SERVER_ERROR";
  }
}

[JoviDeCroock]

For our error extensions to be configurable GraphQLJS/GraphQL.web would have to export that as we are using GraphQLError which has its own definition of extensions. The extensions type in @urql/core is used for ExecutionResult extensions and IncrementalPayloadExtensions which are a different part of the spec.

What you are looking to alter is in this part of the spec and would need altering

• GraphQL.web, which also already exports it
• GraphQL.JS, which already exports it

[musjj]

Thank you for merging the PR (0no-co/graphql.web#36)! Can this repo also be updated with the new version?

[JoviDeCroock]

It's a dependency, you can bump this yourself with resolutions

[musjj]

The latest version does not include the export change: https://www.npmjs.com/package/@0no-co/graphql.web?activeTab=versions. So, graphql.web has to be bumped first.

It looks like that the release workflow hit the rate limit yesterday: https://github.com/0no-co/graphql.web/actions/runs/11626919247/job/32379391261

Can you try re-running it again?

[kitten]

@musjj: We dont't release changes immediately all the time. Please stop commenting for a release that'll come eventually. The action should release a preview version.

Also all of that said, while I understand why @JoviDeCroock has merged this (it's a trivial addition) you really shouldn't be augmenting this type, since there's no type guarantees around error extensions, and should instead write checks and casts for the extensions type.
There's nothing here that's blocking you ✌️