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(gatsby): Protect about possibly missing context in graphql #24108

Merged
merged 5 commits into from
May 15, 2020

Conversation

freiksenet
Copy link
Contributor

@freiksenet freiksenet commented May 15, 2020

Description

This defensively protects about context/info missing in resolver invocation and warns about that, because it's potentially breaking.

Documentation

Related Issues

Fixes #24100

@freiksenet freiksenet requested a review from a team as a code owner May 15, 2020 07:52
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 15, 2020
Copy link
Contributor

@wardpeet wardpeet left a comment

Choose a reason for hiding this comment

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

Perhaps add a test case where you test these messages? And also test the .?tracer change cause seems like it's coming from a bug

packages/gatsby/src/schema/resolvers.ts Outdated Show resolved Hide resolved
packages/gatsby/src/query/utils.ts Show resolved Hide resolved
@wardpeet wardpeet changed the title Protect about possibly missing context fix(gatsby): Protect about possibly missing context in graphql May 15, 2020
Copy link
Contributor

@LekoArts LekoArts left a comment

Choose a reason for hiding this comment

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

LGTM

@freiksenet freiksenet merged commit 9ad511b into master May 15, 2020
@delete-merged-branch delete-merged-branch bot deleted the protect-about-possibly-missing-context branch May 15, 2020 09:56
Kornil pushed a commit to Kornil/gatsby that referenced this pull request May 15, 2020
…yjs#24108)

* Guard against possibly missing context in resolver

* Warn about bad resolver invocations

* Add warning

* Update packages/gatsby/src/schema/resolvers.ts

Co-authored-by: Ward Peeters <[email protected]>

* Fix typo

Co-authored-by: Ward Peeters <[email protected]>
gatsbybot pushed a commit that referenced this pull request May 18, 2020
* Initial conversion

* Add ISetBabelPluginAction

* Fix naming

* Add missing actions

* Add missing plugin type

* Convert babelrc test file to TS

* COnvert snap file as well

* fix(gatsby): Protect about possibly missing context in graphql (#24108)

* Guard against possibly missing context in resolver

* Warn about bad resolver invocations

* Add warning

* Update packages/gatsby/src/schema/resolvers.ts

Co-authored-by: Ward Peeters <[email protected]>

* Fix typo

Co-authored-by: Ward Peeters <[email protected]>

* chore(release): Publish

 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]

* perf(gatsby): enable fast filters for `in` comparator (#24095)

* chore(release): Publish

 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - [email protected]

Co-authored-by: Mikhail Novikov <[email protected]>
Co-authored-by: Ward Peeters <[email protected]>
Co-authored-by: Peter van der Zee <[email protected]>
Co-authored-by: Peter van der Zee <[email protected]>
@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label May 20, 2020
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.

createSchemaCustomization is failing to find tracer in 2.21.31 vs 2.21.19
4 participants