documentation: Add Third Party Schema (#34820)

VividhPandey003 · web-flow · commit 4c832bf3132c · 2022-02-16T08:19:10.000-05:00
Solved issue: #34243
diff --git a/packages/gatsby/src/redux/actions/restricted.ts b/packages/gatsby/src/redux/actions/restricted.ts
@@ -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]
    *

Original file line number	Diff line number	Diff line change
`@@ -37,9 +37,10 @@ export const actions = {`
`37`	`37`	`* Add a third-party schema to be merged into main schema. Schema has to be a`
`38`	`38`	`* graphql-js GraphQLSchema object.`
`39`	`39`	`*`
`40`		`- * This schema is going to be merged as-is. This can easily break the main`
`41`		`- * Gatsby schema, so it's user's responsibility to make sure it doesn't happen`
`42`		`- * (by e.g. namespacing the schema).`
	`40`	`+ * This schema is going to be merged as-is. Merging it in this way will`
	`41`	`+ * easily break the main Gatsby Schema. Since we do not want that, therefore`
	`42`	`+ * it is the user's responsibility to make sure that it does not happen.`
	`43`	`+ * One such way of avoiding it is by namespacing the schema.`
`43`	`44`	`*`
`44`	`45`	`* @availableIn [createSchemaCustomization, sourceNodes]`
`45`	`46`	`*`