feat: added strict server fetcher #46
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new "strict" mode for GraphQL fetchers, which leverages the
graphql-toe
library to improve error handling by throwing errors when attempting to access fields that failed to fetch. In addition, it addsgraphql-toe
as a new dependency and updates related lock files.Strict fetcher implementation and dependency updates:
initStrictServerFetcher
tosrc/server.ts
, which wraps the existing server fetcher and usesgraphql-toe
to enforce strict error handling based on the GraphQL errors array. This ensures that accessing failed fields will throw an error, making error handling more robust.graphql-toe
and related types insrc/server.ts
to support the new strict fetcher. [1] [2]Dependency management:
graphql-toe
as a dependency inpackage.json
and updatedpnpm-lock.yaml
to reflect the new package and its version. [1] [2] [3] [4]Documentation:
.changeset/cuddly-beers-cry.md
) documenting the new strict server and client fetchers and their improved error handling.