From 1426f80081210f8599835e62273950fc8db8bb40 Mon Sep 17 00:00:00 2001 From: Michael Staib Date: Wed, 31 Aug 2022 17:51:54 +0200 Subject: [PATCH] Added new episode to relay docs --- website/src/docs/hotchocolate/defining-a-schema/relay.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/src/docs/hotchocolate/defining-a-schema/relay.md b/website/src/docs/hotchocolate/defining-a-schema/relay.md index d6c9db82b27..8ba32ae5ce5 100644 --- a/website/src/docs/hotchocolate/defining-a-schema/relay.md +++ b/website/src/docs/hotchocolate/defining-a-schema/relay.md @@ -12,6 +12,10 @@ As part of a specification Relay proposes some schema design principles for Grap [Learn more about the Relay GraphQL Server Specification](https://relay.dev/docs/guides/graphql-server-specification) + + # Global identifiers If an output type contains an `id: ID!` field, [Relay](https://relay.dev) and other GraphQL clients will consider this the unique identifier of the entity and might use it to construct a flat cache. This can be problematic, since we could have the same identifier for two of our types. When using a database for example, a `Foo` and `Bar` entity could both contain a row with the identifier `1` in their respective tables.