tinacms 0.68.10 → 0.68.13

package/CHANGELOG.md

@@ -1,1586 +0,0 @@
-# tinacms
-
-## 0.68.10
-
-### Patch Changes
-
-- d95b73974: Fix collection list page delete modal
-- 7b77fe1b5: Add a default TinaMediaStore for repo-based media
-- Updated dependencies [2ef5a1f33]
-- Updated dependencies [fb73fb355]
-- Updated dependencies [7b77fe1b5]
-- Updated dependencies [99a13024d]
-  - @tinacms/toolkit@0.56.33
-  - @tinacms/schema-tools@0.0.6
-  - @tinacms/sharedctx@0.1.1
-
-All notable changes to `tinacms/packages/tinacms` will be documented in this file.
-
-Note: For root tinacms changes, please refer to the [CHANGELOG.md](https://github.com/tinacms/tinacms/CHANGELOG.md) specific to root `tinacms`.
-
-## 0.68.9
-
-### Patch Changes
-
-- 1f7d3ca3d: Use custom wrapper class for tailwind type plugin
-- cceef726e: Fix login ui issue
-- Updated dependencies [1f7d3ca3d]
-- Updated dependencies [f6cb634c2]
-- Updated dependencies [6c17f0160]
-- Updated dependencies [cceef726e]
-  - @tinacms/toolkit@0.56.32
-  - @tinacms/schema-tools@0.0.5
-  - @tinacms/sharedctx@0.1.1
-
-## 0.68.8
-
-### Patch Changes
-
-- 999f0895a: Set font family on heading elements
-- 41be5e7fc: Fixes subitem links to use breadcrumbs
-- Updated dependencies [999f0895a]
-  - @tinacms/toolkit@0.56.31
-
-## 0.68.7
-
-### Patch Changes
-
-- aaaa5bb09: Added pagination to the CMS
-- e06dbb3ca: Adds `waitForDB` cmd to cli
-- Updated dependencies [aaaa5bb09]
-  - @tinacms/toolkit@0.56.30
-
-## 0.68.6
-
-### Patch Changes
-
-- 2cc206b1a: Improve mobile nav behaviour
-- 8998df207: fix: update tina client with the current branch from local storage
-- Updated dependencies [58a7a00f7]
-- Updated dependencies [2cc206b1a]
-- Updated dependencies [aaadefd2d]
-  - @tinacms/toolkit@0.56.29
-
-## 0.68.5
-
-### Patch Changes
-
-- 646cad8da: Adds support for using the generated client on the frontend
-- f857616f6: Rename sdk to queries
-- 6e2ed31a2: Added `isTitle` property to the schema that allows the title to be displayed in the CMS
-- Updated dependencies [a196198bd]
-- Updated dependencies [57a4a3789]
-- Updated dependencies [6e2ed31a2]
-- Updated dependencies [ba1499029]
-  - @tinacms/toolkit@0.56.28
-  - @tinacms/schema-tools@0.0.4
-
-## 0.68.4
-
-### Patch Changes
-
-- 7372f90ca: Adds a new client that can be used on the backend and frontend.
-- Updated dependencies [d4f98d0fc]
-- Updated dependencies [7e2272442]
-  - @tinacms/toolkit@0.56.27
-
-## 0.68.3
-
-### Patch Changes
-
-- 8b7ee346a: - Display label instead of name for mdx dropdown af306fa
-  - Fix issue where reset triggered chagnes to the wrong rich-text field 03f6191
-  - Fix issue where null children in a code block threw an error e454bce
-- Updated dependencies [f6f56bcc0]
-- Updated dependencies [59d33a74a]
-- Updated dependencies [8b7ee346a]
-- Updated dependencies [acb38bf9f]
-  - @tinacms/toolkit@0.56.26
-
-## 0.68.2
-
-### Patch Changes
-
-- Updated dependencies [e90647da3]
-  - @tinacms/toolkit@0.56.25
-
-## 0.68.1
-
-### Patch Changes
-
-- 41d666f9a: Styles list page overflow menu, removes unused prop
-- e5a1152f2: Fix issue where pages that didnt use `useTina` would get a loading spinner that hangs
-- Updated dependencies [41d666f9a]
-  - @tinacms/toolkit@0.56.24
-
-## 0.68.0
-
-### Minor Changes
-
-- 6a6f137ae: # Simplify GraphQL API
-
-  ## `schema` must be supplied to the `<TinaCMS>` component
-
-  Previously the `.tina/schema.ts` was only used by the Tina CLI to generate the GraphQL API. However it's now required as a prop to `<TinaCMS>`. This allows you to provide runtime logic in the `ui` property of field definitions. See the documentation on "Extending Tina" for examples.
-
-  ## The GraphQL API has been simplified
-
-  ### `get<collection name>` is now just the collection name
-
-  ```graphql
-  # old
-  {
-    getPostDocument(relativePath: $relativePath) { ... }
-  }
-
-  # new
-  {
-    post(relativePath: $relativePath) { ... }
-  }
-  ```
-
-  ### `get<collection name>List` is now `<collection name>Connection`
-
-  The use of the term `connection` is due to our adherence the the [relay cursor spec](https://relay.dev/graphql/connections.htm). We may offer a simplified list field in a future release
-
-  ```graphql
-  # old
-  {
-    getPostList { ... }
-  }
-
-  # new
-  {
-    postConnection { ... }
-  }
-  ```
-
-  ### `getCollection` and `getCollections` are now `collection` and `collections`
-
-  ```graphql
-  # old
-  {
-    getCollection(collection: "post") {...}
-  }
-  {
-    getCollections {...}
-  }
-
-  # new
-  {
-    collection(collection: "post") {...}
-  }
-  {
-    collections {...}
-  }
-  ```
-
-  ### No more `data` property
-
-  The `data` property was previously where all field definitions could be found. This has been moved on level up:
-
-  ```graphql
-  # old
-  {
-    getPostDocument(relativePath: $relativePath) {
-      data {
-        title
-      }
-    }
-  }
-
-  # new
-  {
-    post(relativePath: $relativePath) {
-      title
-    }
-  }
-  ```
-
-  #### The type for documents no longer includes "Document" at the end
-
-  ```graphql
-  # old
-  {
-    getPostDocument(relativePath: $relativePath) {
-      data {
-        author {
-          ... on AuthorDocument {
-            data {
-              name
-            }
-          }
-        }
-      }
-    }
-  }
-
-  # new
-  {
-    post(relativePath: $relativePath) {
-      author {
-        ... on Author {
-          name
-        }
-      }
-    }
-  }
-  ```
-
-  ### Meta fields are now underscored
-
-  Aside from `id`, other metadata is now underscored:
-
-  ```graphql
-  # old
-  {
-    getPostDocument(relativePath: $relativePath) {
-      sys {
-        relativePath
-      }
-      values
-    }
-  }
-
-  # new
-  {
-    post(relativePath: $relativePath) {
-      _sys {
-        relativePath
-      }
-      _values
-    }
-  }
-  ```
-
-  ### `dataJSON` is gone
-
-  This is identical to `_values`
-
-  ### `form` is gone
-
-  `form` was used internally to generate forms for the given document, however that's now handled by providing your `schema` to `<TinaCMS>`.
-
-  ### `getDocumentList` is gone
-
-  It's no longer possible to query all documents at once, you can query for collection documents via the `collection` query:
-
-  ```graphql
-  {
-    collection {
-      documents {
-        edges {
-          node {...}
-        }
-      }
-    }
-  }
-  ```
-
-### Patch Changes
-
-- Updated dependencies [6a6f137ae]
-  - @tinacms/toolkit@0.56.23
-
-## 0.67.4
-
-### Patch Changes
-
-- 168f6cc6e: Update delete modal header
-- 2a6060138: Fix url parsing issue when a branch name contained a `/`
-- 3af3d6787: Fix issues with finding the template for multitemplate collections
-- Updated dependencies [bf5fe0074]
-  - @tinacms/toolkit@0.56.22
-
-## 0.67.3
-
-### Patch Changes
-
-- Updated dependencies [d37562999]
-  - @tinacms/toolkit@0.56.21
-
-## 0.67.2
-
-### Patch Changes
-
-- 40afac061: updated @headlessui/react
-- Updated dependencies [40afac061]
-  - @tinacms/toolkit@0.56.20
-
-## 0.67.1
-
-### Patch Changes
-
-- 921709a7e: Adds validation to the schema instead of only using typescript types
-- 3e2d9e43a: Adds new GraphQL `deleteDocument` mutation and logic
-- Updated dependencies [921709a7e]
-  - @tinacms/schema-tools@0.0.3
-
-## 0.67.0
-
-### Minor Changes
-
-- 86651039b: Updates to the way forms are generated in contextual editing. This lays the groundwork for
-  future updates but doesn't offer new behavior yet. It does come with a small breaking change:
-
-  [BREAKING]: The `id` of forms is now the actual document `path`. Previously this was the name of the GraphQL query node (eg. `getPostDocument`).
-  If you're using the [`formifyCallback`](https://tina.io/docs/advanced/customizing-forms/#customizing-a-form) prop to create global forms, you'll probably need to update the callback to check for the appropriate id.
-
-  Eg. `formConfig.id === 'getSiteNavsDocument'` should be something like `formConfig.id === 'content/navs/mynav.md'`
-
-  If you're experiencing any issues with contextual editing, you can disable this flag for now by specifying `cms.flags.set('use-unstable-formify', false)`.
-
-## 0.66.10
-
-### Patch Changes
-
-- 39a8c4f7d: Fix issue with unstableFormify where `Document` interface fields were not being formified properly
-- ec28a129b: Update to tina admin to use the frontend schema
-- a28b787c5: With the rich-text editor, inserting a soft-break (`shift+enter`), this will now result in a `<br>` tag being inserted. Note that this will save the markdown with a backslash to indicate line break (instead of multiple empty spaces):
-
-  ```markdown
-  123 Abc St\
-  Charlottetown, PEI
-  ```
-
-- 93363dfc2: Prevent error on reset when nested blocks have changed in unstable formify hook
-- abf25c673: The schema can now to used on the frontend (optional for now but will be the main path moving forward).
-
-  ### How to migrate.
-
-  If you gone though the `tinacms init` process there should be a file called `.tina/components/TinaProvider`. In that file you can import the schema from `schema.ts` and add it to the TinaCMS wrapper component.
-
-  ```tsx
-  import TinaCMS from 'tinacms'
-  import schema, { tinaConfig } from '../schema.ts'
-
-  // Importing the TinaProvider directly into your page will cause Tina to be added to the production bundle.
-  // Instead, import the tina/provider/index default export to have it dynamially imported in edit-moode
-  /**
-   *
-   * @private Do not import this directly, please import the dynamic provider instead
-   */
-  const TinaProvider = ({ children }) => {
-    return (
-      <TinaCMS {...tinaConfig} schema={schema}>
-        {children}
-      </TinaCMS>
-    )
-  }
-
-  export default TinaProvider
-  ```
-
-- 591640db0: Fixes a bug with `breadcrumbs` to account for subfolders (instead of just the `filename`) and allows Documents to be created and updated within subfolders.
-
-  Before this fix, `breadcrumbs` was only the `basename` of the file minus the `extension`. So `my-folder-a/my-folder-b/my-file.md` would have `breadcrumbs` of `['my-file']`. With this change, `breadcrumbs` will be `['my-folder-a','my-folder-b','my-file']` (leaving out the `content/<collection>`).
-
-- 875779ac6: Don't attempt to formify nodes which don't have data fields (ie. ...on Node)
-- e8b0de1f7: Add `parentTypename` to fields to allow us to disambiguate between fields which have the same field names but different types. Example, an event from field name of `blocks.0.title` could belong to a `Cta` block or a `Hero` block, both of which have a `title` field.
-- Updated dependencies [429d8e93e]
-- Updated dependencies [6c517b5da]
-- Updated dependencies [e81cf8867]
-- Updated dependencies [abf25c673]
-- Updated dependencies [801f39f62]
-- Updated dependencies [0e270d878]
-- Updated dependencies [e8b0de1f7]
-  - @tinacms/sharedctx@0.1.1
-  - @tinacms/toolkit@0.56.19
-  - @tinacms/schema-tools@0.0.2
-
-## 0.66.9
-
-### Patch Changes
-
-- 91d5a6073: Allow "." in file names
-- 11d55f441: Add experimental useGraphQLForms hook
-- f41bd62ea: Ensure client-side Tina code only runs on the browser. Without this check, we'd see a server/client mismatch like:
-
-  ```
-  warning.js:33 Warning: Expected server HTML to contain a matching <div> in <body>.
-  ```
-
-- Updated dependencies [e9a0c82cf]
-- Updated dependencies [d4fdeaa9f]
-- Updated dependencies [ed85f2594]
-- Updated dependencies [d86e515ba]
-- Updated dependencies [db0dab1d4]
-  - @tinacms/toolkit@0.56.18
-
-## 0.66.8
-
-### Patch Changes
-
-- 4923a2d66: Checks isAuthenticated() before making requests to the GraphQL client
-- Updated dependencies [106549814]
-- Updated dependencies [4923a2d66]
-- Updated dependencies [a07ff39bb]
-  - @tinacms/toolkit@0.56.17
-
-## 0.66.7
-
-### Patch Changes
-
-- bfada9a09: Used success messaging when creating/updating a Document in the CMS
-
-## 0.66.6
-
-### Patch Changes
-
-- becff2a0b: Adds define schema to the `tinacms` package (instead of `@tinacms/cli`. This is done in preparation of the extending tina work)
-- ae1a5a58f: Sets `tina-admin` to default to `true`
-- 3ed4c8727: Add flag for experimental new formify logic
-- 5535a9970: Switches to using HashRouter for Admin
-- 3ff1de06a: Upgrade to Tailwind 3
-- fbdb7be01: Adds a defineConfig function to allow type hints for the tinacms config
-- 24f8b057f: Handles errors better in the CMS
-- Updated dependencies [ae1a5a58f]
-- Updated dependencies [5535a9970]
-- Updated dependencies [3ff1de06a]
-- Updated dependencies [022ccd389]
-- Updated dependencies [24f8b057f]
-  - @tinacms/toolkit@0.56.16
-  - @tinacms/sharedctx@0.1.0
-
-## 0.66.5
-
-### Patch Changes
-
-- 43c834565: Adds an activity indicator throughout Admin
-- 53a4550db: Allows RouteMapping to be dynamically imported
-- 731451bee: Adjust the JWT token refresh logic to refresh tokens _before_ they expire.
-- e102d7438: Updated auth modal to use toolkit button components
-- Updated dependencies [43c834565]
-  - @tinacms/toolkit@0.56.15
-
-## 0.66.4
-
-### Patch Changes
-
-- cc5c8431d: Remove console.log
-- Updated dependencies [af9f6c2c2]
-- Updated dependencies [2e14cda5e]
-- Updated dependencies [3d4c52a19]
-  - @tinacms/toolkit@0.56.14
-
-## 0.66.3
-
-### Patch Changes
-
-- Updated dependencies [e41b709ce]
-  - @tinacms/toolkit@0.56.13
-
-## 0.66.2
-
-### Patch Changes
-
-- 102628c7f: Fixes admin page wrapper scrolling
-- 55cb0c5ec: Updates the relativePath field for clarity
-- 9e77273d2: use collection name as fallback for label
-- Updated dependencies [8c18edd5c]
-- Updated dependencies [0773f6486]
-- Updated dependencies [d8cd60f65]
-- Updated dependencies [9e77273d2]
-- Updated dependencies [63a74aece]
-  - @tinacms/toolkit@0.56.12
-
-## 0.66.1
-
-### Patch Changes
-
-- 3bba1817d: Integrates Chrome Components with TinaAdmin
-- Updated dependencies [3bba1817d]
-- Updated dependencies [415c03d25]
-  - @tinacms/toolkit@0.56.11
-  - @tinacms/sharedctx@0.1.0
-
-## 0.66.0
-
-### Minor Changes
-
-- d6f46a9f9: fix: When passing in queries into the root TinaCMS container, don't overwrite the data prop on an empty query
-
-### Patch Changes
-
-- Updated dependencies [37286858e]
-  - @tinacms/toolkit@0.56.10
-
-## 0.65.3
-
-### Patch Changes
-
-- 0c4456c11: fix: Send update to useTina hook on the initial isLoading change
-
-## 0.65.2
-
-### Patch Changes
-
-- a9b385b01: Fix mutation string for document creation
-
-## 0.65.1
-
-### Patch Changes
-
-- 68284198a: fix: use user-specific document creator callback
-- ccf4dcbd4: chore: Export low-level data provider from "tinacms", for the playground and other sandboz environments
-- f2431c031: Fix type for code_block TinaMarkdown element
-
-## 0.65.0
-
-### Minor Changes
-
-- 792f47251: useTina hook for page-level form registration
-
-### Patch Changes
-
-- 6a50a1368: Updates the look and feel of the Tina Sidebar
-- 239382619: Introduces TinaAdminApi and consolidates types
-- Updated dependencies [8ad8f03fd]
-- Updated dependencies [6a50a1368]
-- Updated dependencies [792f47251]
-  - @tinacms/toolkit@0.56.9
-  - @tinacms/sharedctx@0.1.0
-
-## 0.64.2
-
-### Patch Changes
-
-- Updated dependencies [7006b38ea]
-  - @tinacms/toolkit@0.56.8
-
-## 0.64.1
-
-### Patch Changes
-
-- 28010a026: Adds tailwind styles to Admin Layout
-- Updated dependencies [e8ca82899]
-  - @tinacms/toolkit@0.56.7
-
-## 0.64.0
-
-### Minor Changes
-
-- 4a3990c7e: Cloudinary media store now serves images over `https` by default. This can now be configured though the handler provided.
-
-  To revert to the old behavior:
-
-  ```ts
-  export default createMediaHandler(
-    {
-      // ...
-    },
-    {
-      useHttps: false,
-    }
-  )
-  ```
-
-  The default for `useHttps` is `true`
-
-## 0.63.0
-
-### Minor Changes
-
-- 3897ec5d9: Replace `branch`, `clientId`, `isLocalClient` props with single `apiURL`. When working locally, this should be `http://localhost:4001/graphql`. For Tina Cloud, use `https://content.tinajs.io/content/<my-client-id>/github/<my-branch>`
-
-  ```tsx
-  // _app.tsx
-  // ...
-  <TinaCMS apiURL={process.env.NEXT_PUBLIC_TINA_API_URL} {...pageProps}>
-    {livePageProps => <Component {...livePageProps} />}
-  </TinaCMS>
-  ```
-
-  DEPRECATION NOTICE: `branch`, `clientId`, `isLocalClient` props will be deprecated in the future
-
-### Patch Changes
-
-- 96e4a77e2: Fixed types
-- b5c22503a: Changes messaging on login page for TinaAdmin when in local-mode
-- Updated dependencies [60f939f34]
-  - @tinacms/toolkit@0.56.6
-
-## 0.62.0
-
-### Minor Changes
-
-- 70da62fe8: deprecated the use of `getStaticPropsForTina`
-
-### Patch Changes
-
-- 0afa75df1: 2342 - [TinaAdmin] Truncates the `filename` column for the Document List View
-- 7dafce89d: Fixed issue where content creator was invalid
-- 3de8c6165: Enabled branch creation in branch switcher
-- fee183f8f: add "switch to default branch" recover option to error boundary
-- 5c070a83f: feat: Add UI banner for when in localMode
-- Updated dependencies [ddf81a4fd]
-- Updated dependencies [20260a82d]
-- Updated dependencies [0370147fb]
-- Updated dependencies [3de8c6165]
-- Updated dependencies [2eaad97bf]
-- Updated dependencies [5c070a83f]
-  - @tinacms/toolkit@0.56.5
-
-## 0.61.1
-
-### Patch Changes
-
-- Updated dependencies [2c7718636]
-  - @tinacms/toolkit@0.56.4
-
-## 0.61.0
-
-### Minor Changes
-
-- 229feda1d: add .nvmrc file for setting preferred node version
-
-## 0.60.3
-
-### Patch Changes
-
-- 4adaf15af: Fix types which weren't included in previous patch
-
-## 0.60.2
-
-### Patch Changes
-
-- 816271d03: Ensure login/logout pages work when admin flag is disabled
-
-## 0.60.1
-
-### Patch Changes
-
-- Updated dependencies [4700d7ae4]
-  - @tinacms/toolkit@0.56.3
-
-## 0.60.0
-
-### Minor Changes
-
-- 75974d0a4: Updates the tina cloud client to do id_token & access_token refreshes when needed
-
-### Patch Changes
-
-- 88c209b45: Throw when Tina Cloud responds with non 200 code
-- dcdf1ecf0: Updates `react-router` to `v6` for `TinaAdmin`
-- 47d126029: Fix support of objects in a list for MDX templates
-- Updated dependencies [bc4699d2b]
-  - @tinacms/toolkit@0.56.2
-
-## 0.59.1
-
-### Patch Changes
-
-- ed9d48abc: Swaps starter's old admin for the new one
-- f6876d30f: Alter empty sidebar message to be more specific to auto-generating logic
-- Updated dependencies [f6876d30f]
-- Updated dependencies [92268fc85]
-  - @tinacms/toolkit@0.56.1
-
-## 0.59.0
-
-### Minor Changes
-
-- df3030990: Add basic branch switcher
-
-### Patch Changes
-
-- 9ecceb59f: Always include `collection` for TinaAdmin `createDocument()` and `updateDocument()`
-- Updated dependencies [df3030990]
-  - @tinacms/toolkit@0.56.0
-
-## 0.58.1
-
-### Patch Changes
-
-- e6995cfcb: Adds README for TinaAdmin
-- 60729f60c: Adds a `reference` field
-- 19e02829f: Add ability to control plugin layout for global plugins from formify
-- Updated dependencies [60729f60c]
-  - @tinacms/toolkit@0.55.4
-
-## 0.58.0
-
-### Minor Changes
-
-- d1ed404ba: Add support for auto-generated SDK for type-safe data fetching
-
-### Patch Changes
-
-- 138ceb8c4: Clean up dependencies
-- 0417e3750: Adds RouteMapperPlugin and FormMetaPlugin
-- Updated dependencies [138ceb8c4]
-- Updated dependencies [0417e3750]
-- Updated dependencies [d9f37ea7e]
-  - @tinacms/toolkit@0.55.3
-
-## 0.57.4
-
-### Patch Changes
-
-- 4b7795612: Adds support for collection.templates to TinaAdmin
-- a39ddc611: update media store to load only when in edit mode
-- 1096fe3e4: Ensure forms unmount properly when `useGraphQLForms` unmounts
-
-## 0.57.3
-
-### Patch Changes
-
-- Updated dependencies [2724c48c0]
-  - @tinacms/toolkit@0.55.2
-
-## 0.57.2
-
-### Patch Changes
-
-- 7849c1233: Fix styles on panel
-
-## 0.57.1
-
-### Patch Changes
-
-- 9c0d48e09: Fix console errors for mdx editor
-- Updated dependencies [9c0d48e09]
-  - @tinacms/toolkit@0.55.1
-
-## 0.57.0
-
-### Minor Changes
-
-- b99baebf1: Add rich-text editor based on mdx, bump React dependency requirement to 16.14
-
-### Patch Changes
-
-- 891623c7c: Adds support for List and Update to TinaAdmin
-- d5e3adf37: Adds support for Log In & Log Out to TinaAdmin
-- Updated dependencies [b99baebf1]
-  - @tinacms/toolkit@0.55.0
-
-## 0.56.3
-
-### Patch Changes
-
-- 67df49220: Allow dashes in filenames for content creator
-- Updated dependencies [b961c7417]
-  - @tinacms/toolkit@0.54.1
-
-## 0.56.2
-
-### Patch Changes
-
-- 84a86358f: Fix bug which reset the form onChange for GraphQL forms
-
-## 0.56.1
-
-### Patch Changes
-
-- a05aa61bd: Fix issue where forms weren't being removed when the page unmounted
-  - @tinacms/toolkit@0.54.0
-
-## 0.56.0
-
-### Minor Changes
-
-- c6e2dd69a: Updated Wrapper component so that it can be build without loading the media store
-- 3f9cad860: A warning message is added to warn the user if they are using a staticRequest at run time.
-
-### Patch Changes
-
-- 2908f8176: Fixes an issue where nested reference fields weren't updated properly when their values changed.
-- 08ef183a0: Allow tina.io URLs to be supplied as a a prop:
-
-  ```tsx
-  <TinaEditProvider
-    editMode={
-      <TinaCMS
-        branch="main"
-        clientId={NEXT_PUBLIC_TINA_CLIENT_ID}
-        tinaioConfig={{
-          baseUrl: "some-base.io"
-        }}
-        //...
-  ```
-
-  Or just the identity/content URLs:
-
-  ```tsx
-  <TinaEditProvider
-    editMode={
-      <TinaCMS
-        branch="main"
-        clientId={NEXT_PUBLIC_TINA_CLIENT_ID}
-        tinaioConfig={{
-          identityApiUrl: "https://some-base.io"
-          // AND/OR
-          contentApiUrl: "https://content.some-base.io"
-        }}
-        //...
-  ```
-
-- Updated dependencies [9213d5608]
-- Updated dependencies [b59f23295]
-- Updated dependencies [a419056b6]
-- Updated dependencies [ded8dfbee]
-- Updated dependencies [5df9fe543]
-- Updated dependencies [9d68b058f]
-- Updated dependencies [91cebe5bc]
-  - @tinacms/toolkit@0.54.0
-
-## 0.55.2
-
-### Patch Changes
-
-- Updated dependencies [7b149a4e7]
-- Updated dependencies [906d72c50]
-  - @tinacms/toolkit@0.53.0
-
-## 0.55.1
-
-### Patch Changes
-
-- 9b27192fe: Build packages with new scripting, which includes preliminary support for ES modules.
-- Updated dependencies [9b27192fe]
-  - @tinacms/toolkit@0.52.3
-
-## 0.55.0
-
-### Minor Changes
-
-- d0e896561: Provide better error boundary message and visual affordances to user in <ErrorBoundary />.
-- 27c1fd382: Adds a close button to the Tina Cloud auth model so a user is not suck in edit mode.
-
-## 0.54.4
-
-### Patch Changes
-
-- Updated dependencies [6b1cbf916]
-  - @tinacms/toolkit@0.52.2
-
-## 0.54.3
-
-### Patch Changes
-
-- Updated dependencies [4de977f63]
-  - @tinacms/toolkit@0.52.1
-
-## 0.54.2
-
-### Patch Changes
-
-- d1ef2545f: Ensure `undefined` values aren't passed back from getStaticPropsForTina
-
-## 0.54.1
-
-### Patch Changes
-
-- Updated dependencies [b4f5e973f]
-  - @tinacms/toolkit@0.52.0
-
-## 0.54.0
-
-### Minor Changes
-
-- 3af2c075c: Loading state now resets in useGraphqlForms
-- 515fc3ffd: Don't treat cloud client with missing client-id as local client
-
-### Patch Changes
-
-- Updated dependencies [634524925]
-  - @tinacms/toolkit@0.51.0
-
-## 0.53.0
-
-### Minor Changes
-
-- 1b8bb5d0f: fix: don't throw error on missing client id
-
-### Patch Changes
-
-- f863d8be8: Fixes an issue where new documents returned a 404 when on a hosted deployement. Instead, `getStaticPropsForTina` will catch and return an empty object for the data key. This allows us to replace it with real data client-side.
-
-## 0.52.0
-
-### Minor Changes
-
-- 8a20437c: Expose a createGlobalForm function in formifyCallback that creates a screen plugin
-
-### Patch Changes
-
-- d31df43d: Handles situations where `currentFields` is not an Array
-- 271a72d7: Use collection label (defined in schema.ts) as form label
-
-## 0.51.0
-
-### Minor Changes
-
-- 6dfbfed0: Added variables to useGraphqlForms dependencies in order to update data when variables change
-
-### Patch Changes
-
-- Updated dependencies [e074d555]
-  - @tinacms/toolkit@0.50.1
-
-## 0.50.1
-
-### Patch Changes
-
-- 3f05aad1: Fix race condition where `values` was taking longer to update in React state, making the data syncing run too early
-- 76e3a8a7: Properly uses formifyCallback and documentCreatorCallback
-
-## 0.50.0
-
-### Minor Changes
-
-- 7f3c8c1a: # 🔧 Changes coming to TinaCMS ⚙️
-
-  👋 You may have noticed we've been hard at-work lately building out a more opinionated approach to TinaCMS. To that end, we've settled around a few key points we'd like to announce. To see the work in progress, check out the [main](https://github.com/tinacms/tinacms/tree/main) branch, which will become the primary branch soon.
-
-  ## Consolidating @tinacms packages in to @tinacms/toolkit
-
-  By nature, Tina relies heavily on React context, and the dependency mismatches from over-modularizing our toolkit has led to many bugs related to missing context. To fix this, we'll be consolidating nearly every package in the @tinacms scope to a single package called `@tinacms/toolkit`
-
-  We'll also be rolling out esm support as it's now much easier to address build improvements
-
-  ## A more focused tinacms package
-
-  The `tinacms` package now comes baked-in with APIs for working with the TinaCMS GraphQL API. Because `@tinacms/toolkit` now encompasses everything you'd need to build your own CMS integration, we're repurposing the `tinacms` package to more accurately reflect the "batteries-included" approach.
-
-  If you haven't been introduced, the GraphQL API is a Git-backed CMS which we'll be leaning into more in the future. With a generous free tier and direct syncing with Github its something we're really excited to push forward. Sign up for free here
-  Note: tinacms still exports the same APIs, but we'll gradually start moving the backend-agnostic tools to @tinacms/toolkit.
-
-  ## Consolidating the tina-graphql-gateway repo
-
-  The tina-graphql-gateway repo will be absorbed into this one. If you've been working with our GraphQL APIs you'll need to follow our migration guide.
-
-  ## Moving from Lerna to Yarn PNP
-
-  We've had success with Yarn 2 and PNP in other monorepos, if you're a contributor you'll notice some updates to the DX, which should hopefully result in a smoother experience.
-
-  ## FAQ
-
-  ### What about other backends?
-
-  The `@tinacms/toolkit` isn't going anywhere. And if you're using packages like `react-tinacms-strapi` or r`eact-tinacms-github` with success, that won't change much, they'll just be powered by `@tinacms/toolkit` under the hood.
-
-  ### Do I need to do anything?
-
-  We'll be bumping all packages to `0.50.0` to reflect the changes. If you're using @tincams scoped packages those won't receive the upgrade. Unscoped packages like `react-tinacms-editor` will be upgraded, and should be bumped to 0.50.0 as well.
-  When we move to `1.0.0` we'll be pushing internal APIs to `@tinacms/toolkit`, so that's the long-term location of
-
-  ### Will you continue to patch older versions?
-
-  We'll continue to make security patches, however major bug fixes will likely not see any updates. Keep in mind that `@tinacms/toolkit` will continue to be developed.
-
-### Patch Changes
-
-- 434d61d4: Use the default import from 'tinacms' to set up the Tina context:
-
-  ```jsx
-  // pages/_app.js
-  import TinaCMS from 'tinacms'
-
-  const App = ({ Component, pageProps }) => {
-    return (
-      <TinaCMS
-        // Required: The query from your `getStaticProps` request
-        query={pageProps.query}
-        // Required: The variables from your `getStaticProps` request
-        variables={pageProps.variables} // Variables used in your query
-        // Required: The data from your `getStaticProps` request
-        data={pageProps.data}
-        // Optional: Set to true when working with the local API
-        isLocalClient={true}
-        // Optional: When using Tina Cloud, specify the git branch
-        branch="main"
-        // Optional: Your identifier when connecting to Tina Cloud
-        clientId="<some-id-from-tina-cloud>"
-        // Optional: A callback for altering the CMS object if needed
-        cmsCallback={cms => {}}
-        // Optional: A callback for altering the form generation if needed
-        formifyCallback={args => {}}
-        // Optional: A callback for altering the document creator plugin
-        documentCreatorCallback={args => {}}
-      >
-        {livePageProps => <Component {...livePageProps} />}
-      </TinaCMS>
-    )
-  }
-
-  export default App
-  ```
-
-  To load TinaCMS dynamically, use the EditState context:
-
-  ```jsx
-  // pages/_app.js
-  import dynamic from 'next/dynamic'
-  import { TinaEditProvider } from 'tinacms/dist/edit-state'
-  const TinaCMS = dynamic(() => import('tinacms'), { ssr: false })
-
-  const App({ Component, pageProps }) {
-    return (
-      <>
-        <TinaEditProvider
-          editMode={
-            <TinaCMS {...pageProps}>
-              {livePageProps => <Component {...livePageProps} />}
-            </TinaCMS>
-          }
-        >
-          <Component {...pageProps} />
-        </TinaEditProvider>
-      </>
-    )
-  }
-
-  export default App
-  ```
-
-- Updated dependencies [7f3c8c1a]
-  - @tinacms/toolkit@0.44.0
-
-## 0.4.0
-
-### Minor Changes
-
-- ab4e388b: Updates where LoadingDots is imported from
-- 7351d92f: # Define schema changes
-
-  We're going to be leaning on a more _primitive_ concept of how types are defined with Tina, and in doing so will be introducing some breaking changes to the way schemas are defined. Read the detailed [RFC discussion](https://github.com/tinacms/rfcs/pull/18) for more on this topic, specifically the [latter portions](https://github.com/tinacms/rfcs/pull/18#issuecomment-805400313) of the discussion.
-
-  ## Collections now accept a `fields` _or_ `templates` property
-
-  You can now provide `fields` instead of `templates` for your collection, doing so will result in a more straightforward schema definition:
-
-  ```js
-  {
-    collections: [
-      {
-        name: 'post',
-        label: 'Post',
-        path: 'content/posts',
-        fields: [
-          {
-            name: 'title',
-            label: 'Title',
-            type: 'string', // read on below to learn more about _type_ changes
-          },
-        ],
-        // defining `fields` and `templates` would result in a compilation error
-      },
-    ]
-  }
-  ```
-
-  **Why?**
-
-  Previously, a collection could define multiple templates, the ambiguity introduced with this feature meant that your documents needed a `_template` field on them so we'd know which one they belonged to. It also mean having to disambiguate your queries in graphql:
-
-  ```graphql
-  getPostDocument(relativePage: $relativePath) {
-    data {
-      ...on Article_Doc_Data {
-        title
-      }
-    }
-  }
-  ```
-
-  Going forward, if you use `fields` on a collection, you can omit the `_template` key and simplify your query:
-
-  ```graphql
-  getPostDocument(relativePage: $relativePath) {
-    data {
-      title
-    }
-  }
-  ```
-
-  ## `type` changes
-
-  Types will look a little bit different, and are meant to reflect the lowest form of the shape they can represent. Moving forward, the `ui` field will represent the UI portion of what you might expect. For a blog post "description" field, you'd define it like this:
-
-  ```js
-  {
-    type: "string",
-    label: "Description",
-    name: "description",
-  }
-  ```
-
-  By default `string` will use the `text` field, but you can change that by specifying the `component`:
-
-  ```js
-  {
-    type: "string",
-    label: "Description",
-    name: "description",
-    ui: {
-      component: "textarea"
-    }
-  }
-  ```
-
-  For the most part, the UI properties are added to the field and adhere to the existing capabilities of Tina's core [field plugins](https://tina.io/docs/fields/). But there's nothing stopping you from providing your own components -- just be sure to register those with the CMS object on the frontend:
-
-  ```js
-  {
-    type: "string",
-    label: "Description",
-    name: "description",
-    ui: {
-      component: "myMapField"
-      someAdditionalMapConfig: 'some-value'
-    }
-  }
-  ```
-
-  [Register](https://tina.io/docs/fields/custom-fields/#registering-the-plugin) your `myMapField` with Tina:
-
-  ```js
-  cms.fields.add({
-    name: 'myMapField',
-    Component: MapPicker,
-  })
-  ```
-
-  ### One important gotcha
-
-  Every property in the `defineSchema` API must be serlializable. Meaning functions will not work. For example, there's no way to define a `validate` or `parse` function at this level. However, you can either use the [formify](https://tina.io/docs/tina-cloud/client/#formify) API to get access to the Tina form, or provide your own logic by specifying a plugin of your choice:
-
-  ```js
-  {
-    type: "string",
-    label: "Description",
-    name: "description",
-    ui: {
-      component: "myText"
-    }
-  }
-  ```
-
-  And then when you register the plugin, provide your custom logic here:
-
-  ```js
-  import { TextFieldPlugin } from 'tinacms'
-
-  // ...
-
-  cms.fields.add({
-    ...TextFieldPlugin, // spread existing text plugin
-    name: 'myText',
-    validate: value => {
-      someValidationLogic(value)
-    },
-  })
-  ```
-
-  **Why?**
-
-  The reality is that under the hood this has made no difference to the backend, so we're removing it as a point of friction. Instead, `type` is the true definition of the field's _shape_, while `ui` can be used for customizing the look and behavior of the field's UI.
-
-  ## Defensive coding in Tina
-
-  When working with GraphQL, there are 2 reasons a property may not be present.
-
-  1. The data is not a required property. That is to say, if I have a blog post document, and "category" is an optional field, we'll need to make sure we factor that into how we render our page:
-
-  ```tsx
-  const MyPage = props => {
-    return (
-      <>
-        <h2>{props.getPostDocument.data.title}</h2>
-        <MyCategoryComponent>
-          {props.getPostDocument.data?.category}
-        </MyCategoryComponent>
-      </>
-    )
-  }
-  ```
-
-  2. The query did not ask for that field:
-
-  ```graphql
-  {
-    getPostDocument {
-      data {
-        title
-      }
-    }
-  }
-  ```
-
-  But with Tina, there's a 3rd scenario: the document may be in an invalid state. Meaning, we could mark the field as `required` _and_ query for the appropriate field, and _still_ not have the expected shape of data. Due to the contextual nature of Tina, it's very common to be in an intermediate state, where your data is incomplete simply because you're still working on it. Most APIs would throw an error when a document is in an invalid state. Or, more likely, you couldn't even request it.
-
-  ## Undefined list fields will return `null`
-
-  Previously an listable field which wasn't defined in the document was treated as an emptry array. So for example:
-
-  ```md
-  ---
-  title: 'Hello, World'
-  categories:
-    - sports
-    - movies
-  ---
-  ```
-
-  The responsee would be `categories: ['sports', 'movies']`. If you omit the items, but kept the empty array:
-
-  ```md
-  ---
-  title: 'Hello, World'
-  categories: []
-  ---
-  ```
-
-  The responsee would be `categories: []`. If you omit the field entirely:
-
-  ```md
-  ---
-  title: 'Hello, World'
-  ---
-  ```
-
-  The response will be `categories: null`. Previously this would have been `[]`, which was incorrect.
-
-  ## For a listable item which is `required: true` you _must_ provide a `ui.defaultItem` property
-
-  ### Why?
-
-  It's possible for Tina's editing capabilities to introduce an invalid state during edits to list items. Imagine the scenario where you are iterating through an array of objects, and each object has a categories array on it we'd like to render:
-
-  ```tsx
-  const MyPage = props => {
-    return props.blocks.map(block => {
-      return (
-        <>
-          <h2>{block.categories.split(',')}</h2>
-        </>
-      )
-    })
-  }
-  ```
-
-  For a new item, `categories` will be null, so we'll get an error. This only happens when you're editing your page with Tina, so it's not a production-facing issue.
-
-  ## Every `type` can be a list
-
-  Previously, we had a `list` field, which allowed you to supply a `field` property. Instead, _every_ primitive type can be represented as a list:
-
-  ```js
-  {
-    type: "string",
-    label: "Categories",
-    name: "categories",
-    list: true
-  }
-  ```
-
-  Additionally, enumerable lists and selects are inferred from the `options` property. The following example is represented by a `select` field:
-
-  ```js
-  {
-    type: "string",
-    label: "Categories",
-    name: "categories",
-    options: ["fitness", "movies", "music"]
-  }
-  ```
-
-  While this, is a `checkbox` field
-
-  ```js
-  {
-    type: "string",
-    label: "Categories",
-    name: "categories"
-    list: true,
-    options: ["fitness", "movies", "music"]
-  }
-  ```
-
-  > Note we may introduce an `enum` type, but haven't discussed it thoroughly
-
-  ## Introducing the `object` type
-
-  Tina currently represents the concept of an _object_ in two ways: a `group` (and `group-list`), which is a uniform collection of fields; and `blocks`, which is a polymporphic collection. Moving forward, we'll be introducing a more comporehensive type, which envelopes the behavior of both `group` and `blocks`, and since _every_ field can be a `list`, this also makes `group-list` redundant.
-
-  > Note: we've previously assumed that `blocks` usage would _always_ be as an array. We'll be keeping that assumption with the `blocks` type for compatibility, but `object` will allow for non-array polymorphic objects.
-
-  ### Defining an `object` type
-
-  An `object` type takes either a `fields` _or_ `templates` property (just like the `collections` definition). If you supply `fields`, you'll end up with what is essentially a `group` item. And if you say `list: true`, you'll have what used to be a `group-list` definition.
-
-  Likewise, if you supply a `templates` field and `list: true`, you'll get the same API as `blocks`. However you can also say `list: false` (or omit it entirely), and you'll have a polymorphic object which is _not_ an array.
-
-  This is identical to the current `blocks` definition:
-
-  ```js
-  {
-    type: "object",
-    label: "Page Sections",
-    name: "pageSections",
-    list: true,
-    templates: [{
-      label: "Hero",
-      name: "hero",
-      fields: [{
-        label: "Title",
-        name: "title",
-        type: "string"
-      }]
-    }]
-  }
-  ```
-
-  And here is one for `group`:
-
-  ```js
-  {
-    type: "object",
-    label: "Hero",
-    name: "hero",
-    fields: [{
-      label: "Title",
-      name: "title",
-      type: "string"
-    }]
-  }
-  ```
-
-  ## `dataJSON` field
-
-  You can now request `dataJSON` for the entire data object as a single query key. This is great for more tedius queries like theme files where including each item in the result is cumbersome.
-
-  > Note there is no typescript help for this feature for now
-
-  ```graphql
-  getThemeDocument(relativePath: $relativePath) {
-    dataJSON
-  }
-  ```
-
-  ```json
-  {
-    "getThemeDocument": {
-      "dataJSON": {
-        "every": "field",
-        "in": {
-          "the": "document"
-        },
-        "is": "returned"
-      }
-    }
-  }
-  ```
-
-  ## Lists queries will now adhere to the GraphQL connection spec
-
-  [Read the spec](https://relay.dev/graphql/connections.htm)
-
-  Previously, lists would return a simple array of items:
-
-  ```graphql
-  {
-    getPostsList {
-      id
-    }
-  }
-  ```
-
-  Which would result in:
-
-  ```json
-  {
-    "data": {
-      "getPostsList": [
-        {
-          "id": "content/posts/voteForPedro.md"
-        }
-      ]
-    }
-  }
-  ```
-
-  In the new API, you'll need to step through `edges` & `nodes`:
-
-  ```graphql
-  {
-    getPostsList {
-      edges {
-        node {
-          id
-        }
-      }
-    }
-  }
-  ```
-
-  ```json
-  {
-    "data": {
-      "getPostsList": {
-        "edges": [
-          {
-            "node": {
-              "id": "content/posts/voteForPedro.md"
-            }
-          }
-        ]
-      }
-    }
-  }
-  ```
-
-  **Why?**
-
-  The GraphQL connection spec opens up a more future-proof structure, allowing us to put more information in to the _connection_ itself like how many results have been returned, and how to request the next page of data.
-
-  Read [a detailed explanation](https://graphql.org/learn/pagination/) of how the connection spec provides a richer set of capabilities.
-
-  > Note: sorting and filtering is still not supported for list queries.
-
-  ## `_body` is no longer included by default
-
-  There is instead an `isBody` boolean which can be added to any `string` field
-
-  **Why?**
-
-  Since markdown files sort of have an implicit "body" to them, we were automatically populating a field which represented the body of your markdown file. This wasn't that useful, and kind of annoying. Instead, just attach `isBody` to the field which you want to represent your markdown "body":
-
-  ```js
-  {
-    collections: [{
-      name: "post",
-      label: "Post",
-      path: "content/posts",
-      fields: [
-        {
-          name: "title",
-          label: "Title",
-          type: "string"
-        }
-        {
-          name: "myBody",
-          label: "My Body",
-          type: "string",
-          component: 'textarea',
-          isBody: true
-        }
-      ]
-    }]
-  }
-  ```
-
-  This would result in a form field called `My Body` getting saved to the body of your markdown file (if you're using markdown):
-
-  ```md
-  ---
-  title: Hello, World!
-  ---
-
-  This is the body of the file, it's edited through the "My Body" field in your form.
-  ```
-
-  ## References now point to more than one collection.
-
-  Instead of a `collection` property, you must now define a `collections` field, which is an array:
-
-  ```js
-  {
-    type: "reference",
-    label: "Author",
-    name: "author",
-    collections: ["author"]
-  }
-  ```
-
-  ```graphql
-  {
-    getPostDocument(relativePath: "hello.md") {
-      data {
-        title
-        author {
-          ...on Author_Document {
-            name
-          }
-          ...on Post_Document {
-            title
-          }
-        }
-      }
-    }
-  ```
-
-  ## Other breaking changes
-
-  ### The `template` field on polymorphic objects (formerly _blocks_) is now `_template`
-
-  **Old API:**
-
-  ```md
-  ---
-  ---
-  myBlocks:
-    - template: hero
-      title: Hello
-  ---
-  ```
-
-  **New API:**
-
-  ```md
-  ---
-  ---
-  myBlocks:
-    - \_template: hero
-      title: Hello
-  ---
-  ```
-
-  ### `data` `__typename` values have changed
-
-  They now include the proper namespace to prevent naming collisions and no longer require `_Doc_Data` suffix. All generated `__typename` properties are going to be slightly different. We weren't fully namespacing fields so it wasn't possible to guarantee that no collisions would occur. The pain felt here will likely be most seen when querying and filtering through blocks. This ensures the stability of this type in the future
-
-  ```graphql
-  {
-    getPageDocument(relativePath: "home.md") {
-      data {
-        title
-        myBlocks {
-          ...on Page_Hero_Data {  # previously this would have been Hero_Data
-            # ...
-          }
-        }
-      }
-    }
-  ```
-
-### Patch Changes
-
-- d42e2bcf: Adds number, datetime, and boolean fields back into primitive field generators
-- 95244e14: Early return for query nodes which can't be formified
-- Updated dependencies [7351d92f]
-  - tina-graphql-helpers@0.1.2
-
-## 0.3.0
-
-### Minor Changes
-
-- 96ee3eb1: Revisited useDocumentCreatorPlugin to improve the UX
-
-## 0.2.23
-
-### Patch Changes
-
-- Bump packages to reflect new changest capabilities
-- Updated dependencies [undefined]
-  - tina-graphql-helpers@0.1.1
-
-## 0.2.22
-
-### Patch Changes
-
-- Updated dependencies [undefined]
-  - tina-graphql-helpers@0.1.0