-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Support engine.graphVariant and APOLLO_GRAPH_VARIANT. #3924
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
7968837
Add deprecation warning for engine.schemaTag
756639e
Revert "Add deprecation warning for engine.schemaTag"
b4a20be
Revert "Revert "Add deprecation warning for engine.schemaTag""
4aa8e40
Revert docs change, fix docs
e88976e
Move calculation of graphVariant into agent
8e4bf7a
Add mock of console.warn to test
e34789b
Add changelog entry
1eee85a
Add CHANGELOG entries
2c18ded
Merge branch 'master' into adam/20/3/support-graph-variant
zionts 3383b8e
Merge branch 'master' into adam/20/3/support-graph-variant
zionts 0a3f799
Update CHANGELOG.md
zionts 7d9bd3e
Apply Jesse's suggestion from code review
zionts 96e1ceb
Update packages/apollo-server-core/src/__tests__/ApolloServerBase.tes…
zionts 6f6f0c9
Update packages/apollo-server-core/src/__tests__/ApolloServerBase.tes…
zionts 00b7962
Merge branch 'master' into adam/20/3/support-graph-variant
zionts 05d80cf
Use custom logger
75918ca
Merge branch 'master' into adam/20/3/support-graph-variant
zionts ebf8474
Merge branch 'master' into adam/20/3/support-graph-variant
zionts a852ea8
Merge branch 'master' into adam/20/3/support-graph-variant
zionts 54095f0
Merge branch 'master' into adam/20/3/support-graph-variant
abernix File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could be more specific here and test for what we don't want thrown, in terms of specific error message. Otherwise this test ends up failing when some other thing which intentionally fails this pattern crops up, red herring during development, etc. We can avoid that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the flip side, it means that if someone changes the error message, then the test which is looking for it will continue to pass silently, but will be doing nothing, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zionts A defensive best-of-both-worlds technique would be test for each and have the tests rely on the same error message string.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But like... what error message are we looking for? I can think of a couple different error messages that are reasonable to test for.
Will we actually keep this up to date as we add more? Will it actually be a red herring as opposed to a good test update, when we add, e.g. "throw on malformed API key" that causes this test to error?
I would really prefer to leave this as just making sure this configuration doesn't throw anything and updating the test + adding another if another behavior through a different feature causes this test to throw.