@tinacms/schema-tools 0.0.0-dced6ab-20250611061422 → 0.0.0-dde3eb3-20251028070343

package/dist/types/index.d.ts

@@ -3,6 +3,21 @@ import type React from 'react';
 export declare const CONTENT_FORMATS: readonly ["mdx", "md", "markdown", "json", "yaml", "yml", "toml"];
 export type ContentFormat = (typeof CONTENT_FORMATS)[number];
 export type ContentFrontmatterFormat = 'yaml' | 'toml' | 'json';
+export type Parser = {
+    type: 'mdx';
+} | {
+    type: 'markdown';
+    /**
+     * Tina will escape entities like `<` and `[` by default. You can choose to turn
+     * off all escaping, or specify HTML, so `<div>` will not be turned into `\<div>`
+     */
+    skipEscaping?: 'all' | 'html' | 'none';
+} | {
+    /**
+     * Experimental: Returns the native Slate.js document as JSON. Ideal to retain the pure editor content structure.
+     */
+    type: 'slatejson';
+};
 type Meta = {
     active?: boolean;
     dirty?: boolean;
@@ -114,6 +129,11 @@ export type UIField<Type, List extends boolean> = {
 type FieldGeneric<Type, List extends boolean | undefined, ExtraFieldUIProps = {}> = List extends true ? {
     list: true;
     ui?: UIField<Type, true> & ExtraFieldUIProps;
+    /**
+     * Defines where new items will be added in the list.
+     * If not specified, defaults to `append`.
+     */
+    addItemBehavior?: 'append' | 'prepend';
 } : List extends false ? {
     list?: false;
     ui?: UIField<Type, false> & ExtraFieldUIProps;
@@ -215,16 +235,7 @@ export type RichTextField<WithNamespace extends boolean = false> = (FieldGeneric
      *
      * Specify `"markdown"` if you're having problems with Tina parsing your content.
      */
-    parser?: {
-        type: 'markdown';
-        /**
-         * Tina will escape entities like `<` and `[` by default. You can choose to turn
-         * off all escaping, or specify HTML, so `<div>` will not be turned into `\<div>`
-         */
-        skipEscaping?: 'all' | 'html' | 'none';
-    } | {
-        type: 'mdx';
-    };
+    parser?: Parser;
 };
 export type RichTextTemplate<WithNamespace extends boolean = false> = Template<WithNamespace> & {
     inline?: boolean;
@@ -380,7 +391,7 @@ export interface Config<CMSCallback = undefined, FormifyCallback = undefined, Do
     /**
      * The Schema is used to define the shape of the content.
      *
-     * https://tina.io/docs/reference/schema/
+     * https://tina.io/docs/r/the-config-file/
      */
     schema: Schema;
     /**
@@ -417,11 +428,17 @@ export interface Config<CMSCallback = undefined, FormifyCallback = undefined, Do
          * ```
          * [more info](https://vercel.com/docs/concepts/deployments/generated-urls#url-with-git-branch)
          */
-        previewUrl: (context: {
+        previewUrl?: (context: {
             branch: string;
         }) => {
             url: string;
         };
+        /**
+         * Opt out of update checks - this will prevent the CMS for checking for new versions
+         * If true, the CMS will not check for updates.
+         * Defaults to false if not specified.
+         */
+        optOutOfUpdateCheck?: boolean;
     };
     /**
      * Configurations for the autogenerated GraphQL HTTP client
@@ -501,7 +518,7 @@ export interface Config<CMSCallback = undefined, FormifyCallback = undefined, Do
     } | {
         /**
          * Use Git-backed assets for media, these values will
-         * [Learn more](https://tina.io/docs/reference/media/repo-based/)
+         * [Learn more](https://tina.io/docs/r/repo-based-media/)
          */
         tina: {
             /**
@@ -576,7 +593,7 @@ export interface Schema<WithNamespace extends boolean = false> {
     /**
      * Collections represent a type of content (EX, blog post, page, author, etc). We recommend using singular naming in a collection (Ex: use post and not posts).
      *
-     * https://tina.io/docs/reference/collections/
+     * https://tina.io/docs/r/content-modelling-collections/
      */
     collections: Collection<WithNamespace>[];
     /**
@@ -615,7 +632,7 @@ type TemplateCollection<WithNamespace extends boolean = false> = {
     /**
      * In most cases, just using fields is enough, however templates can be used when there are multiple variants of the same collection or object. For example in a "page" collection there might be a need for a marketing page template and a content page template, both under the collection "page".
      *
-     * https://tina.io/docs/reference/templates/
+     * https://tina.io/docs/r/content-modelling-templates/
      */
     templates: Template<WithNamespace>[];
     fields?: undefined;
@@ -624,7 +641,7 @@ type FieldCollection<WithNamespace extends boolean = false> = {
     /**
      * Fields define the shape of the content and the user input.
      *
-     * https://tina.io/docs/reference/fields/
+     * https://tina.io/docs/r/string-fields/
      */
     fields: TinaField<WithNamespace>[];
     templates?: undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tinacms/schema-tools",
-  "version": "0.0.0-dced6ab-20250611061422",
+  "version": "0.0.0-dde3eb3-20251028070343",
   "main": "dist/index.js",
   "module": "./dist/index.mjs",
   "exports": {
@@ -32,7 +32,7 @@
     "ts-jest": "^29.2.5",
     "typescript": "^5.7.3",
     "yup": "^0.32.11",
-    "@tinacms/scripts": "0.0.0-dced6ab-20250611061422"
+    "@tinacms/scripts": "0.0.0-dde3eb3-20251028070343"
   },
   "peerDependencies": {
     "react": ">=16.14.0",