@tinacms/datalayer 0.2.0 → 0.2.3

package/LICENSE

@@ -0,0 +1,176 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/dist/database/bridge/filesystem.d.ts

@@ -30,5 +30,5 @@ export declare class FilesystemBridge implements Bridge {
  * Same as the `FileSystemBridge` except it does not save files
  */
 export declare class AuditFileSystemBridge extends FilesystemBridge {
-    put(_filepath: string, _data: string): Promise<void>;
+    put(filepath: string, data: string): Promise<void>;
 }

package/dist/database/store/index.d.ts

@@ -140,5 +140,5 @@ export declare const makeFilterSuffixes: (filterChain: (BinaryFilter | TernaryFi
     left?: string;
     right?: string;
 } | undefined;
-export declare const makeKeyForField: (definition: IndexDefinition, data: object, stringEscaper: StringEscaper) => string | null;
+export declare const makeKeyForField: (definition: IndexDefinition, data: object, stringEscaper: StringEscaper, maxStringLength?: number) => string | null;
 export {};

package/dist/index.js

@@ -51,7 +51,7 @@ var __toModule = (module2) => {
   return __reExport(__markAsModule(__defProp(module2 != null ? __create(__getProtoOf(module2)) : {}, "default", module2 && module2.__esModule && "default" in module2 ? { get: () => module2.default, enumerable: true } : { value: module2, enumerable: true })), module2);
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/index.ts
+// src/index.ts
 __export(exports, {
   AuditFileSystemBridge: () => AuditFileSystemBridge,
   AuditFilesystemStore: () => AuditFilesystemStore,
@@ -73,7 +73,7 @@ __export(exports, {
   makeStringEscaper: () => makeStringEscaper
 });
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/bridge/filesystem.ts
+// src/database/bridge/filesystem.ts
 var import_fs_extra = __toModule(require("fs-extra"));
 var import_fast_glob = __toModule(require("fast-glob"));
 var import_path = __toModule(require("path"));
@@ -109,17 +109,25 @@ var FilesystemBridge = class {
   }
 };
 var AuditFileSystemBridge = class extends FilesystemBridge {
-  async put(_filepath, _data) {
+  async put(filepath, data) {
+    if ([
+      ".tina/__generated__/_lookup.json",
+      ".tina/__generated__/_schema.json",
+      ".tina/__generated__/_graphql.json"
+    ].includes(filepath)) {
+      return super.put(filepath, data);
+    }
     return;
   }
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/bridge/isomorphic.ts
+// src/database/bridge/isomorphic.ts
 var import_isomorphic_git = __toModule(require("isomorphic-git"));
 var import_fs_extra2 = __toModule(require("fs-extra"));
 var import_glob_parent = __toModule(require("glob-parent"));
 var import_normalize_path2 = __toModule(require("normalize-path"));
 var import_graphql = __toModule(require("graphql"));
+var import_path2 = __toModule(require("path"));
 var flat = typeof Array.prototype.flat === "undefined" ? (entries) => entries.reduce((acc, x) => acc.concat(x), []) : (entries) => entries.flat();
 var toUint8Array = (buf) => {
   const ab = new ArrayBuffer(buf.length);
@@ -208,9 +216,18 @@ var IsomorphicBridge = class {
     let pathParts = path4.split("/");
     const result = await import_isomorphic_git.default.walk(__spreadProps(__spreadValues({}, this.isomorphicConfig), {
       map: async (filepath, [head]) => {
-        if (head._fullpath === "." || path4.startsWith(filepath)) {
+        if (head._fullpath === ".") {
           return head;
         }
+        if (path4.startsWith(filepath)) {
+          if ((0, import_path2.dirname)(path4) === (0, import_path2.dirname)(filepath)) {
+            if (path4 === filepath) {
+              return head;
+            }
+          } else {
+            return head;
+          }
+        }
       },
       cache: this.cache,
       trees: [import_isomorphic_git.default.TREE({ ref })]
@@ -431,16 +448,16 @@ var IsomorphicBridge = class {
   }
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/store/filesystem.ts
+// src/database/store/filesystem.ts
 var import_fs_extra3 = __toModule(require("fs-extra"));
 var import_fast_glob2 = __toModule(require("fast-glob"));
-var import_path2 = __toModule(require("path"));
+var import_path3 = __toModule(require("path"));
 var import_normalize_path3 = __toModule(require("normalize-path"));
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/util.ts
+// src/database/util.ts
 var import_gray_matter = __toModule(require("gray-matter"));
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/util.ts
+// src/util.ts
 var yup = __toModule(require("yup"));
 var import_graphql2 = __toModule(require("graphql"));
 var sequential = async (items, callback) => {
@@ -479,7 +496,7 @@ var btoa = (string) => {
   return Buffer.from(string).toString("base64");
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/util.ts
+// src/database/util.ts
 var stringifyFile = (content, format, keepTemplateKey) => {
   switch (format) {
     case ".markdown":
@@ -534,7 +551,7 @@ var parseFile = (content, format, yupSchema) => {
   }
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/store/filesystem.ts
+// src/database/store/filesystem.ts
 var FilesystemStore = class {
   async clear() {
   }
@@ -550,7 +567,7 @@ var FilesystemStore = class {
     throw new Error(`Seeding data is not possible for Filesystem store`);
   }
   async get(filepath) {
-    return parseFile(await import_fs_extra3.default.readFileSync(import_path2.default.join(this.rootPath, filepath)).toString(), import_path2.default.extname(filepath), (yup2) => yup2.object());
+    return parseFile(await import_fs_extra3.default.readFileSync(import_path3.default.join(this.rootPath, filepath)).toString(), import_path3.default.extname(filepath), (yup2) => yup2.object());
   }
   supportsSeeding() {
     return false;
@@ -559,8 +576,8 @@ var FilesystemStore = class {
     return false;
   }
   async glob(pattern, callback, extension) {
-    const basePath = import_path2.default.join(this.rootPath, ...pattern.split("/"));
-    const itemsRaw = await (0, import_fast_glob2.default)(import_path2.default.join(basePath, "**", `/*${extension}`).replace(/\\/g, "/"), {
+    const basePath = import_path3.default.join(this.rootPath, ...pattern.split("/"));
+    const itemsRaw = await (0, import_fast_glob2.default)(import_path3.default.join(basePath, "**", `/*${extension}`).replace(/\\/g, "/"), {
       dot: true
     });
     const posixRootPath = (0, import_normalize_path3.default)(this.rootPath);
@@ -576,14 +593,14 @@ var FilesystemStore = class {
     }
   }
   async put(filepath, data, options) {
-    await import_fs_extra3.default.outputFileSync(import_path2.default.join(this.rootPath, filepath), stringifyFile(data, import_path2.default.extname(filepath), options.keepTemplateKey));
+    await import_fs_extra3.default.outputFileSync(import_path3.default.join(this.rootPath, filepath), stringifyFile(data, import_path3.default.extname(filepath), options.keepTemplateKey));
   }
   async open() {
   }
   async close() {
   }
   async delete(filepath) {
-    await import_fs_extra3.default.remove(import_path2.default.join(this.rootPath, filepath));
+    await import_fs_extra3.default.remove(import_path3.default.join(this.rootPath, filepath));
   }
 };
 var AuditFilesystemStore = class extends FilesystemStore {
@@ -592,7 +609,7 @@ var AuditFilesystemStore = class extends FilesystemStore {
   }
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/store/index.ts
+// src/database/store/index.ts
 var import_jsonpath_plus = __toModule(require("jsonpath-plus"));
 var DEFAULT_COLLECTION_SORT_KEY = "__filepath__";
 var INDEX_KEY_FIELD_SEPARATOR = "#";
@@ -921,11 +938,12 @@ var makeFilterSuffixes = (filterChain, index) => {
     return {};
   }
 };
-var makeKeyForField = (definition, data, stringEscaper) => {
+var makeKeyForField = (definition, data, stringEscaper, maxStringLength = 100) => {
   const valueParts = [];
   for (const field of definition.fields) {
-    if (field.name in data) {
-      const resolvedValue = String(field.type === "datetime" ? new Date(data[field.name]).getTime() : field.type === "string" ? stringEscaper(data[field.name]) : data[field.name]);
+    if (field.name in data && data[field.name] !== void 0 && data[field.name] !== null) {
+      const rawValue = data[field.name];
+      const resolvedValue = String(field.type === "datetime" ? new Date(rawValue).getTime() : field.type === "string" ? stringEscaper(rawValue) : rawValue).substring(0, maxStringLength);
       valueParts.push(applyPadding(resolvedValue, field.pad));
     } else {
       return null;
@@ -934,8 +952,8 @@ var makeKeyForField = (definition, data, stringEscaper) => {
   return valueParts.join(INDEX_KEY_FIELD_SEPARATOR);
 };
 
-// pnp:/home/runner/work/tinacms/tinacms/packages/@tinacms/datalayer/src/database/store/level.ts
-var import_path3 = __toModule(require("path"));
+// src/database/store/level.ts
+var import_path4 = __toModule(require("path"));
 var import_level = __toModule(require("level"));
 var import_levelup = __toModule(require("levelup"));
 var import_memdown = __toModule(require("memdown"));
@@ -949,7 +967,7 @@ var LevelStore = class {
     if (useMemory) {
       this.db = (0, import_levelup.default)((0, import_encoding_down.default)((0, import_memdown.default)(), { valueEncoding: "json" }));
     } else {
-      this.db = (0, import_level.default)(import_path3.default.join(rootPath, ".tina/__generated__/db"), {
+      this.db = (0, import_level.default)(import_path4.default.join(rootPath, ".tina/__generated__/db"), {
         valueEncoding: "json"
       });
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tinacms/datalayer",
-  "version": "0.2.0",
+  "version": "0.2.3",
   "main": "dist/index.js",
   "typings": "dist/index.d.ts",
   "files": [
@@ -17,11 +17,6 @@
       }
     ]
   },
-  "scripts": {
-    "types": "yarn tsc",
-    "build": "echo \"Run `yarn build` from the root of the repository instead\"",
-    "test": "jest --passWithNoTests"
-  },
   "dependencies": {
     "@octokit/auth-app": "^2.6.0",
     "@octokit/graphql": "^4.5.6",
@@ -52,7 +47,7 @@
     "directory": "packages/@tinacms/datalayer"
   },
   "devDependencies": {
-    "@tinacms/scripts": "0.50.9",
+    "@tinacms/scripts": "0.51.1",
     "@types/fs-extra": "^9.0.2",
     "@types/jest": "^27.4.1",
     "@types/js-yaml": "^3.12.5",
@@ -67,6 +62,11 @@
     "jest-diff": "27.0.6",
     "jest-file-snapshot": "^0.5.0",
     "jest-matcher-utils": "27.0.6",
-    "typescript": "^4.3.5"
+    "typescript": "4.3.5"
+  },
+  "scripts": {
+    "types": "pnpm tsc",
+    "build": "tinacms-scripts build",
+    "test": "jest --passWithNoTests"
   }
 }

package/CHANGELOG.md

@@ -1,864 +0,0 @@
-# tina-graphql
-
-## 0.2.0
-
-### Minor Changes
-
-- 4daf15b36: Updated matching logic to only return the correct extension.
-
-  This means if you are using any other files besides `.md` the format must be provided in the schema.
-
-  ```ts
-  // .tina/schema.ts
-
-  import { defineSchema } from 'tinacms'
-
-  const schema = defineSchema({
-    collections: [
-      {
-        name: 'page',
-        path: 'content/page',
-        label: 'Page',
-        // Need to provide the format if the file being used (default is `.md`)
-        format: 'mdx',
-        fields: [
-          //...
-        ],
-      },
-    ],
-  })
-  //...
-
-  export default schema
-  ```
-
-### Patch Changes
-
-- b348f8b6b: Experimental isomorphic git bridge implementation
-
-## 0.1.1
-
-### Patch Changes
-
-- a2906d6fe: Fix datetime filtering to handle both indexed and non-indexed queries
-- 3e2d9e43a: Adds new GraphQL `deleteDocument` mutation and logic
-
-## 0.1.0
-
-### Minor Changes
-
-- a87e1e6fa: Enable query filtering, pagination, sorting
-
-### Patch Changes
-
-- 8b3be903f: Escape index field separator in input strings
-- b01f2e382: Fixed an issue where `0` as a numerical operand was being evaluated as falsy.
-
-## 0.0.2
-
-### Patch Changes
-
-- b399c734c: Fixes support for collection.templates in graphql
-
-## 0.0.1
-
-### Patch Changes
-
-- 80732bd97: Create a @tinacms/datalayer package which houses the logic for data management for the GraphQL API. This simplifies the @tinacms/graphql package and allows for a clearer separation.
-
-## 0.59.1
-
-### Patch Changes
-
-- f46c6f987: Fix type definitions for schema metadata so they're optional
-
-## 0.59.0
-
-### Minor Changes
-
-- 62bea7019: #2323: fix saving bold and italic text in rich-text editor
-
-### Patch Changes
-
-- bd4e1f802: Pin version number from @tinacms/graphql during schema compilation. This can be used to ensure the proper version is provided when working with Tina Cloud
-
-## 0.58.2
-
-### Patch Changes
-
-- fffce3af8: Don't cache graphql schema during resolution, this was causing the schema to go stale, while updating the schema.gql, so GraphQL tooling thought the value was updated, but the server was still holding on to the cached version
-
-## 0.58.1
-
-### Patch Changes
-
-- 4700d7ae4: Patch fix to ensure builds include latest dependencies
-
-## 0.58.0
-
-### Minor Changes
-
-- fa7a0419f: Adds experimental support for a data layer between file-based content and the GraphQL API. This allows documents to be indexed so the CMS can behave more like a traditional CMS, with the ability enforce foreign reference constraints and filtering/pagination capabilities.
-
-### Patch Changes
-
-- eb5fbfac7: Ensure GraphQL resolve doesn't access "bridge" documents
-- 47d126029: Fix support of objects in a list for MDX templates
-
-## 0.57.2
-
-### Patch Changes
-
-- edb2f4011: Trim path property on collections during compilation
-
-## 0.57.1
-
-### Patch Changes
-
-- 60729f60c: Adds a `reference` field
-
-## 0.57.0
-
-### Minor Changes
-
-- ed277e3bd: Remove aws dependency and cache logic from GithubBridge
-- d1ed404ba: Add support for auto-generated SDK for type-safe data fetching
-
-### Patch Changes
-
-- 138ceb8c4: Clean up dependencies
-- 577d6a5ad: Adds collection arg back for generic queries as optional
-
-## 0.56.1
-
-### Patch Changes
-
-- 4b7795612: Adds support for collection.templates to TinaAdmin
-
-## 0.56.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
-
-## 0.55.2
-
-### Patch Changes
-
-- 9ecb392ca: Fix bug which would set markdown body to undefined when the payload was emptry"
-
-## 0.55.1
-
-### Patch Changes
-
-- ff4446c8e: Adds `getDocumentFields()` query for use with Tina Admin
-- 667c33e2a: Add support for rich-text field, update build script to work with unified packages, which are ESM-only
-
-## 0.55.0
-
-### Minor Changes
-
-- f3bddeb4a: Added new warning messages for list UI that we do not support by default
-
-### Patch Changes
-
-- 2908f8176: Fixes an issue where nested reference fields weren't updated properly when their values changed.
-- 5d83643b2: Adds create document mutations
-
-## 0.54.3
-
-### Patch Changes
-
-- 9b27192fe: Build packages with new scripting, which includes preliminary support for ES modules.
-
-## 0.54.2
-
-### Patch Changes
-
-- d94fec611: Improve exported types for defineSchema
-
-## 0.54.1
-
-### Patch Changes
-
-- 4de977f63: Makes `DateFieldPlugin` timezone-friendly
-
-## 0.54.0
-
-### Minor Changes
-
-- 7663e0f7f: Fixed windows issue where you could not save a file
-
-## 0.53.0
-
-### Minor Changes
-
-- b4f5e973f: Update datetime field to expect and receive ISO string
-
-## 0.52.2
-
-### Patch Changes
-
-- b4bbdda86: Better error messaging when no tina schema files are found
-
-## 0.52.1
-
-### Patch Changes
-
-- b05c91c6: Remove console.log
-
-## 0.52.0
-
-### Minor Changes
-
-- aa4507697: When working with a new document that queries for a reference, we were not properly building the path information required to update that reference, resulting in an error until the page was refreshed.
-
-## 0.51.1
-
-### Patch Changes
-
-- 589c7806: Fix issue where the `isBody` field wasn't properly removing that value from frontmatter. Ensure that the field is not treating any differently for JSON format
-
-## 0.51.0
-
-### Minor Changes
-
-- 5a934f6b: Fixed windows path issues
-
-### Patch Changes
-
-- 271a72d7: Use collection label (defined in schema.ts) as form label
-
-## 0.50.2
-
-### Patch Changes
-
-- 0970961f: addPendingDocument was expecting params, which are not supported for new doc creation at this time
-
-## 0.50.1
-
-### Patch Changes
-
-- 65b3e3a3: Uses checkbox-group field
-
-## 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.
-
-## 0.2.0
-
-### Minor Changes
-
-- 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
-
-- fdb7724b: Fix stringify for json extensions
-- d42e2bcf: Adds number, datetime, and boolean fields back into primitive field generators
-- 5cd5ce76: - Improve types for ui field
-  - Marks system fields as required so the user has a guarantee that they'll be there
-  - Return null for listable fields which are null or undefined
-  - Handle null values for reference fields better
-- 8c425440: Remmove accidental additional of dataJSON in schema
-- Updated dependencies [7351d92f]
-  - tina-graphql-helpers@0.1.2
-
-## 0.1.25
-
-### Patch Changes
-
-- 348ef1e5: Testing version bumps go into a PR
-
-## 0.1.24
-
-### Patch Changes
-
-- b36de960: lruClearCache should just be clearCache for now
-
-## 0.1.23
-
-### Patch Changes
-
-- Bump packages to reflect new changest capabilities
-- Updated dependencies [undefined]
-  - tina-graphql-helpers@0.1.1
-
-## 0.1.22
-
-### Patch Changes
-
-- Updated dependencies [undefined]
-  - tina-graphql-helpers@0.1.0
-
-## 0.1.21
-
-### Patch Changes
-
-- Testin
-
-## 0.1.20
-
-### Patch Changes
-
-- Testing
-
-## 0.1.13
-
-### Patch Changes
-
-- Testing out changesets