fix(mapSchema): allow custom serialization function #5120
Closed
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.
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
Checks to see if a custom serialization function has been added during
mapSchema
, and ensures this new serialization function is added to the rewired type.Related #5119
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
Example repo showing the bug https://github.com/rupert648/graphql-tools-serialization-bug-demo
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
mapSchema.test.ts
to ensure this functionality is appliedTest Environment:
@graphql-tools/schema : "9.0.13"
Checklist: