From ea53e2afe5851d9ca95d41f6ee57c9ecb958bbcc Mon Sep 17 00:00:00 2001 From: Alvaro Bueno Date: Fri, 4 Feb 2022 14:09:50 -0500 Subject: [PATCH] fix: giving proper format to guide on GraphQL queries Signed-off-by: Alvaro Bueno Signed-off-by: Brent Hoover --- guides/create-graphql-query.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/create-graphql-query.md b/guides/create-graphql-query.md index 3980255..8e34b6a 100644 --- a/guides/create-graphql-query.md +++ b/guides/create-graphql-query.md @@ -6,9 +6,9 @@ In this guide, we’ll guide you through the steps you need to create a successf The complete Reaction Commerce GraphQL API is created by stitching together domain-specific APIs from all of the API plugins. So when adding a new query, the first step is to decide which plugin should own it. This is usually obvious, but not always. You should think about whether any other plugins or services will need to call your query. If the query is fundamental to the system, then it may need to go in the "core" plugin, if no better alternative exists. -## Understand the difference between a plugin query function and a GraphQL query resolver +## Understand the difference between a plugin mutation function and a GraphQL mutation resolver -See [Resolver Mutations and Queries vs. Plugin Mutations and Queries](../guides/developers-guide/core/developing-graphql.md#resolver-mutations-and-queries-vs-plugin-mutations-and-queries) +See [Resolver mutations and queries vs. plugin mutations and queries in the GraphQL concepts docs](.docs/graphql-concepts.md) ## Name the query