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

a-e-r: Add missing peer dependency on graphql. #3496

Merged
merged 4 commits into from
Nov 27, 2019

Conversation

arcanis
Copy link
Contributor

@arcanis arcanis commented Nov 11, 2019

apollo-engine-reporting has a transitive peer dependency on graphql through apollo-graphql, apollo-server-types, and graphql-extensions, and must be marked as such. Cf my article why implicit transitive peer dependencies are bad 🙂

As long as you're here, can you please give a look to the following related PRs? 😃

The `apollo-engine-reporting` package was absolutely missing its
`peerDependencies` specification for `graphql`.  The previous commit added
it, but we also need to expand it to match the same range as suggested by
the rest of the Apollo packages in the Apollo Server monorepo.

Ref: https://git.io/JeXBd
Copy link
Member

@abernix abernix left a comment

Choose a reason for hiding this comment

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

Thank you very much for opening this! I made a couple follow-up commits to widen the version range to match that of the other packages in this monorepo, as well as the addition of a CHANGELOG entry.

(I can't promise I'll be able to merge the other PRs of a similar spirit, but I'll try to spread the word. 😉)

@abernix abernix changed the title Adds missing peer dependency a-e-r: Add missing peer dependency on graphql. Nov 27, 2019
@abernix abernix merged commit a12a0bf into apollographql:master Nov 27, 2019
@arcanis
Copy link
Contributor Author

arcanis commented Nov 27, 2019

Awesome, thanks 😊

@abernix abernix added this to the Release 2.9.13 milestone Dec 17, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants