Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change federation codegen to use output type where relevant. #9770

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

meiamsome
Copy link

Description

These types come over from other servers, and so should use types from the output, not the internal Parent type.

Related #5646, see for more information

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

I don't think this is breaking because anyone who is using the current behaviour that would be changed by this must necessarily have incorrect types.

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

  • Changes to unit tests
  • Used yarn link to test this out in a Federation service to check it works as intended

Test Environment:

  • OS: Mac OS X 13.6.2
  • @graphql-codegen/...: master branch
  • NodeJS: v18.15.0

Checklist:

  • I have followed the CONTRIBUTING doc and the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
    I don't think any are required
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
    No such changes

Further comments

None
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

These types come over from other servers, and so should use types from the output, not the internal side of the resolvers.
Copy link

changeset-bot bot commented Nov 29, 2023

🦋 Changeset detected

Latest commit: 025eaa6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@graphql-codegen/typescript-resolvers Patch
@graphql-codegen/plugin-helpers Patch

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

@meiamsome meiamsome marked this pull request as ready for review November 29, 2023 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant