[client-preset] Forward immutableTypes option to client preset#10459
Merged
Conversation
🦋 Changeset detectedLatest commit: 2abc148 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
eddeee888
commented
Oct 6, 2025
Collaborator
Author
There was a problem hiding this comment.
I think I didn't commit yarn.lock correctly in the last PR, so when running yarn in this PR, it cleans up the lockfile like this.
eddeee888
changed the title
Contributor
Contributor
💻 Website PreviewThe latest changes are available as preview in: https://pr-10459.graphql-code-generator.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
immutableTypesis a good option to pass through because it forces users handle responses as immutable. Majority of users would use a client such as Apollo Client which manages its own caching which shouldn't be mutated in any way.Related: #8296 (comment)
Type of change
How Has This Been Tested?