Fix issue here source directive was not getting mapped to the correct types after multiple transformations #7790
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
The
@source
directives are added to the schema before schema transformations. Hence, need to be remapped after possible renames, replacements, and type merging. This was not happening with the existing code causing the@source
directives to point to type names that either no longer existed (due to rename merges) or were pointing to the wrong type (type replacement transforms).This fix introduces changes to the field mapper that happens after transformations, and make sure to map the
@source
directives to the correct or existing types.Fixes #7771
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take
action on it as appropriate
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
Test Environment:
@graphql-mesh/1.1.0
:Checklist:
CONTRIBUTING doc and the
style guidelines of this project
changeset using
yarn changeset
that bumps the version