From bb7d447213fff6c1c49082d0735e7f0a6a3cfe95 Mon Sep 17 00:00:00 2001 From: katiegoines Date: Wed, 18 Oct 2023 10:37:11 -0700 Subject: [PATCH] filter out all but android --- src/pages/lib/graphqlapi/relational/q/platform/[platform].mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/pages/lib/graphqlapi/relational/q/platform/[platform].mdx b/src/pages/lib/graphqlapi/relational/q/platform/[platform].mdx index 2f6622d3ddf..0a9ff943603 100644 --- a/src/pages/lib/graphqlapi/relational/q/platform/[platform].mdx +++ b/src/pages/lib/graphqlapi/relational/q/platform/[platform].mdx @@ -3,6 +3,8 @@ export const meta = { description: `Learn more about how API (GraphQL) handles relationships between Models, such as "has one", "has many", "belongs to".` }; + + API (GraphQL) has the capability to handle relationships between Models, such as _has one_, _has many_, and _belongs to_. In Amplify GraphQL APIs, this is done with the `@hasOne`, `@hasMany` and `@belongsTo` directives as defined in the [GraphQL data modeling documentation](/cli/graphql/data-modeling). By default, GraphQL APIs requests generate a selection set with a depth of 0. Connected relationship models are not returned in the initial request, but can be lazily loaded as needed with an additional API request. We provide mechanisms to customize the selection set, which allows connected relationships to be eagerly loaded on the initial request. @@ -833,3 +835,5 @@ This query fetches a postEditor and eagerly loads its post and comments + +