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

Fix merging of renamed @tag directive ... #1637

Merged
merged 3 commits into from
Mar 25, 2022

Conversation

pcmanus
Copy link
Contributor

@pcmanus pcmanus commented Mar 23, 2022

... but requires that it is renamed consistently in all subgraphs.

}

const MERGED_FEDERATION_DIRECTIVES: MergedDirectiveInfo[] = [
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If someone wonders why this patch is kind of over-generic despite only have 1 merged directive, that's because @inaccessible will be add to this list shortly.

@netlify
Copy link

netlify bot commented Mar 23, 2022

👷 Deploy request for apollo-federation-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit c6f6653

@codesandbox-ci
Copy link

codesandbox-ci bot commented Mar 23, 2022

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Sylvain Lebresne added 2 commits March 24, 2022 16:04
... but requires that it is renamed consistently in all subgraphs.
Copy link
Contributor

@clenfest clenfest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I question a bit whether this needs to be an error in the long term or if we can just do something smart, but I guess it could lead to confusion when examinging the supergraph if naming is inconsistent. Otherwise LGTM.

@pcmanus pcmanus merged commit c65bb66 into apollographql:main Mar 25, 2022
@pcmanus
Copy link
Contributor Author

pcmanus commented Mar 25, 2022

I question a bit whether this needs to be an error in the long term or if we can just do something smart

And for the record, I agree with that questioning. This PR is meant to be a stop-gap until we figure out the full rules we want for merging core directives.

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

2 participants