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.

Sign up for GitHub

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

Jump to bottom

docs(gatsby): Add Third Party Schema #34820

Merged
merged 2 commits into from
Feb 16, 2022
Merged

docs(gatsby): Add Third Party Schema #34820

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a87bcd5
documentation: Add Third Party Schema
VividhPandey003 Feb 13, 2022
0389d73
Merge pull request #2 from VividhPandey003/VividhPandey003-patch-2
VividhPandey003 Feb 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions packages/gatsby/src/redux/actions/restricted.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,10 @@ export const actions = {
* Add a third-party schema to be merged into main schema. Schema has to be a
* graphql-js GraphQLSchema object.
*
* This schema is going to be merged as-is. This can easily break the main
* Gatsby schema, so it's user's responsibility to make sure it doesn't happen
* (by e.g. namespacing the schema).
* This schema is going to be merged as-is. Merging it in this way will
* easily break the main Gatsby Schema. Since we do not want that, therefore
* it is the user's responsibility to make sure that it does not happen.
* One such way of avoiding it is by namespacing the schema.
*
* @availableIn [createSchemaCustomization, sourceNodes]
*
Expand Down