From 15ae411c35668a47570822144d89489b4bdde258 Mon Sep 17 00:00:00 2001 From: "gento.ogane" Date: Thu, 9 Nov 2023 19:00:14 +0900 Subject: [PATCH] [#11305]update fragments doc --- docs/source/data/fragments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/data/fragments.md b/docs/source/data/fragments.md index d90178584ef..dadecba00b2 100644 --- a/docs/source/data/fragments.md +++ b/docs/source/data/fragments.md @@ -100,7 +100,7 @@ Starting in Apollo Client 3.7, fragments can be registered with your `InMemoryCa Let's look at an example in React. -```js title="index.js" {7-12} +```jsx title="main.jsx" {7-12} import { ApolloClient, gql, InMemoryCache } from "@apollo/client"; import { createFragmentRegistry } from "@apollo/client/cache"; @@ -143,7 +143,7 @@ function ToDoList() { Queries can declare their own local versions of named fragments which will take precendence over ones registered via `createFragmentRegistry`, even if the local fragment is only indirectly referenced by other registered fragments. Take the following example: -```js title="index.js" {7-17} +```jsx title="main.jsx" {7-17} import { ApolloClient, gql, InMemoryCache } from "@apollo/client"; import { createFragmentRegistry } from "@apollo/client/cache";