-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Clarify how to properly namespace a schema to use with addThirdParty schema. #34243
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
Comments
|
Hi, thanks for the issue. PRs improving this are appreciated! |
|
Hey, I am a beginner and first time contributing to open source. I found this documentation issue which I think I can maybe rectify but I wanted a bit of guidance regarding the same. |
Hey!, I think @dopry wanted to say that Gatsby schema, so it's user's responsibility to make sure it doesn't happen should be written as Gatsby schema, so it's the user's responsibility to make sure it doesn't happen. Correct me if I am wrong. |
|
This comment has been minimized.
This comment has been minimized.
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
|
Hey again! It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |


Preliminary Checks
Summary
I am working on a source plugin and encountering issues using addThirdPartySchema. It is unclear what the documentation means by namespacing a schema.
see:
gatsby/packages/gatsby/src/redux/actions/restricted.ts
Line 41 in af6632b
The article is missing after
it's user's responsibility.It would be nice to drop the use of the conjunctive'sfollowed by the possessive'sfor non-native speakers who may not parse this easily. This could readit is the user's responsibility.Steps to Resolve this Issue
The text was updated successfully, but these errors were encountered: