@tinacms/schema-tools 1.3.2 → 1.3.4

package/dist/types.d.ts

@@ -1,556 +0,0 @@
-/**
-
-*/
-declare type Doc = {
-    _sys: {
-        title?: string;
-        template: string;
-        breadcrumbs: string[];
-        path: string;
-        basename: string;
-        relativePath: string;
-        filename: string;
-        extension: string;
-    };
-};
-/**
- *
- */
-export interface UICollection {
-    filename?: {
-        /**
-         * A callback which receives form values as an argument. The return value
-         * here will be used as the filename (the extension is not necessary)
-         *
-         * eg:
-         * ```ts
-         * slugify: (values) => values.title.toLowerCase().split(" ").join("-")
-         * ```
-         */
-        slugify?: (values: Record<string, any>) => string;
-        /**
-         * When set to `true`, editors won't be able to modify the filename
-         */
-        readonly?: boolean;
-    };
-    /**
-     * Forms for this collection will be editable from the global sidebar rather than the form panel
-     */
-    global?: boolean | {
-        icon?: any;
-        layout: 'fullscreen' | 'popup';
-    };
-    /**
-     * Provide the path that your document is viewable on your site
-     *
-     * eg:
-     * ```ts
-     * router: ({ document }) => {
-     *   return `blog-posts/${document._sys.filename}`;
-     * }
-     * ```
-     */
-    router?: (args: {
-        document: Doc;
-        collection: Collection;
-    }) => string | undefined;
-    /**
-     * Determines whether or not this collection can accept new docments
-     * or allow documents to be deleted from the CMS.
-     */
-    allowedActions?: {
-        create?: boolean;
-        delete?: boolean;
-    };
-}
-export declare type Option = string | {
-    label: string;
-    value: string;
-};
-import type React from 'react';
-declare type Meta = {
-    active?: boolean;
-    dirty?: boolean;
-    error?: any;
-};
-declare type Component<Type, List> = (props: {
-    field: SchemaField & {
-        namespace: string[];
-    };
-    input: {
-        /**
-         * The full name of the field, for fields nested inside object
-         * fields, this will be the full path:
-         *
-         * `myObject.0.title`
-         */
-        name: string;
-        onBlur: (event?: React.FocusEvent<Type>) => void;
-        /**
-         * The value provided will be saved to the form so it
-         * should match the configured type:
-         *
-         * `input.onChange('some string')`
-         */
-        onChange: (event: React.ChangeEvent<Type>) => void;
-        onFocus: (event?: React.FocusEvent<Type>) => void;
-        type?: string;
-        value: List extends true ? Type[] : Type;
-    };
-    meta: Meta;
-}) => any;
-declare type UIField<Type, List extends boolean> = {
-    max?: List extends true ? number : never;
-    min?: List extends true ? number : never;
-    /**
-     * Override the label from parent object
-     */
-    label?: string;
-    /**
-     * Override the description from parent object
-     */
-    description?: string;
-    /**
-     * A React component which will be used in the Tina form. Be sure
-     * to import React into the config file.
-     *
-     * Note: Any Tailwind classes provided here will be compiled as part
-     * of the Tina stylesheet
-     *
-     * eg:
-     * ```tsx
-     *  component: (props) => {
-     *    const { input, field } = props
-     *    return (
-     *      <div className="my-4">
-     *        <label
-     *          htmlFor={input.name}
-     *          className="block text-sm font-medium"
-     *        >
-     *          {field.name}
-     *        </label>
-     *        <div className="mt-1">
-     *          <input
-     *            id={input.name}
-     *            className="py-2 px-4 block"
-     *            type="text"
-     *            {...input}
-     *          />
-     *        </div>
-     *      </div>
-     *    )
-     *  }
-     * ```
-     *
-     * Note: If the form has already been registered with the cms, you
-     * can provide it's name here (eg. `textarea`)
-     */
-    component?: Component<Type, List> | string | null;
-    /**
-     * Optional: Prepare data for use in the component. This is useful
-     * if you don't have access to the component directly
-     */
-    parse?: (value: List extends true ? Type[] : Type, name: string, field: Field) => List extends true ? Type[] : Type;
-    /**
-     * Optional: Prepare data for saving. This is useful
-     * if you don't have access to the component directly
-     */
-    format?: (value: Type, name: string, field: Field) => List extends true ? Type[] : Type;
-    /**
-     * Optional: Return undefined when valid. Return a string or an object when there are errors.
-     *
-     * ```ts
-     * validate: (value) => {
-     *   if(value.length > 40){
-     *      return 'Title cannot be more than 40 characters long'
-     *   }
-     * }
-     * ```
-     */
-    validate?(value: List extends true ? Type[] : Type, allValues: {
-        [key: string]: any;
-    }, meta: Meta, field: UIField<Type, List>): string | void;
-    /**
-     * @deprecated use `defaultItem` at the collection level instead
-     */
-    defaultValue?: List extends true ? Type[] : Type;
-};
-declare type FieldGeneric<Type, List extends boolean | undefined, ExtraFieldUIProps = {}> = List extends true ? {
-    list: true;
-    ui?: UIField<Type, true> & ExtraFieldUIProps;
-} : List extends false ? {
-    list?: false;
-    ui?: UIField<Type, false> & ExtraFieldUIProps;
-} : {
-    list?: undefined;
-    ui?: UIField<Type, false> & ExtraFieldUIProps;
-};
-export interface BaseField {
-    label?: string | boolean;
-    required?: boolean;
-    name: string;
-    description?: string;
-}
-export declare type StringField = (FieldGeneric<string, undefined> | FieldGeneric<string, true> | FieldGeneric<string, false>) & BaseField & {
-    type: 'string';
-    isTitle?: boolean;
-    options?: Option[];
-};
-export declare type NumberField = (FieldGeneric<number, undefined> | FieldGeneric<number, true> | FieldGeneric<number, false>) & BaseField & {
-    type: 'number';
-};
-export declare type BooleanField = (FieldGeneric<boolean, undefined> | FieldGeneric<boolean, true> | FieldGeneric<boolean, false>) & BaseField & {
-    type: 'boolean';
-};
-declare type DateFormatProps = {
-    /**
-     * Customize the way the format is rendered
-     * ```
-     * dateFormat: 'YYYY MM DD'
-     * ```
-     */
-    dateFormat?: string;
-    timeFormat?: string;
-};
-export declare type DateTimeField = (FieldGeneric<string, undefined, DateFormatProps> | FieldGeneric<string, true, DateFormatProps> | FieldGeneric<string, false, DateFormatProps>) & BaseField & {
-    type: 'datetime';
-};
-export declare type ImageField = (FieldGeneric<string, undefined> | FieldGeneric<string, true> | FieldGeneric<string, false>) & BaseField & {
-    type: 'image';
-};
-export declare type ReferenceField = (FieldGeneric<string, undefined> | FieldGeneric<string, false>) & BaseField & {
-    type: 'reference';
-    /**
-     * The names of the collections this field can use as a reference
-     * ```ts
-     * {
-     *   type: 'reference',
-     *   name: 'author',
-     *   collections: ['author'],
-     * }
-     * ```
-     */
-    collections: string[];
-};
-declare type RichTextAst = {
-    type: 'root';
-    children: Record<string, unknown>[];
-};
-export declare type RichTextField = (FieldGeneric<RichTextAst, undefined> | FieldGeneric<RichTextAst, false>) & BaseField & {
-    type: 'rich-text';
-    /**
-     * When using Markdown or MDX formats, this field's value
-     * will be saved to the markdown body, while all other values
-     * will be stored as frontmatter
-     */
-    isBody?: boolean;
-    templates?: (Template & {
-        inline?: boolean;
-        /**
-         * If you have some custom shortcode logic in your markdown,
-         * you can specify it in the 'match' property and Tina will
-         * handle it as if it were a jsx element:
-         *
-         * ```
-         * # This is my markdown, it uses some custom shortcode
-         * syntax {{ myshortcode title="hello!" }}.
-         *
-         * {
-         *   match: {
-         *     start: "{{"
-         *     end: "}}"
-         *   }
-         * }
-         * ```
-         */
-        match?: {
-            start: string;
-            end: string;
-            name?: string;
-        };
-    })[];
-    /**
-     * By default, Tina parses markdown with MDX, this is a more strict parser
-     * that allows you to use structured content inside markdown (via `templates`).
-     *
-     * 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';
-    };
-};
-declare type DefaultItem<ReturnType> = ReturnType | (() => ReturnType);
-declare type ObjectUiProps = {
-    visualSelector?: boolean;
-};
-export declare type ObjectField = (FieldGeneric<string, undefined, ObjectUiProps> | FieldGeneric<string, true, ObjectUiProps> | FieldGeneric<string, false, ObjectUiProps>) & BaseField & ({
-    type: 'object';
-    fields: Field[];
-    templates?: undefined;
-    ui?: Template['ui'];
-} | {
-    type: 'object';
-    fields?: undefined;
-    templates: Template[];
-});
-declare type Field = StringField | NumberField | BooleanField | DateTimeField | ImageField | ReferenceField | RichTextField | ObjectField;
-declare type SchemaField = Field;
-export type { SchemaField };
-export interface Template {
-    label?: string;
-    name: string;
-    ui?: {
-        /**
-         * Override the properties passed to the field
-         * component. This is mostly useful for controlling
-         * the display value via callback on `itemProps.label`
-         */
-        itemProps?(item: Record<string, any>): {
-            key?: string;
-            /**
-             * Control the display value when object
-             * items are shown in a compact list, eg:
-             *
-             * ```ts
-             * itemProps: (values) => ({
-             *   label: values?.title || 'Showcase Item',
-             * }),
-             * ```
-             */
-            label?: string;
-        };
-        defaultItem?: DefaultItem<Record<string, any>>;
-        /**
-         * When used in relation to the `visualSelector`,
-         * provide an image URL to be used as the preview
-         * in the blocks selector menu
-         */
-        previewSrc?: string;
-    };
-    fields: Field[];
-}
-export interface FieldCollection {
-    label?: string;
-    name: string;
-    path: string;
-    format?: 'json' | 'md' | 'markdown' | 'mdx' | 'yaml' | 'yml' | 'toml';
-    /**
-     * This format will be used to parse the markdown frontmatter
-     */
-    frontmatterFormat?: 'yaml' | 'toml' | 'json';
-    /**
-     * The delimiters used to parse the frontmatter.
-     */
-    frontmatterDelimiters?: [string, string] | string;
-    ui?: UICollection & {
-        defaultItem?: DefaultItem<Record<string, any>>;
-    };
-    /**
-     * @deprecated - use `ui.defaultItem` instead
-     */
-    defaultItem?: DefaultItem<Record<string, any>>;
-    templates?: never;
-    /**
-     * Fields define the shape of the content and the user input.
-     *
-     * https://tina.io/docs/reference/fields/
-     */
-    fields: Field[];
-}
-export interface TemplateCollection {
-    label?: string;
-    name: string;
-    path: string;
-    format?: 'json' | 'md' | 'markdown' | 'mdx' | 'yaml' | 'yml' | 'toml';
-    ui?: UICollection;
-    /**
-     * @deprecated - use `ui.defaultItem` on the each `template` instead
-     */
-    defaultItem?: DefaultItem<Record<string, any>>;
-    /**
-     * 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/
-     */
-    templates?: Template[];
-    fields?: never;
-}
-export declare type Collection = FieldCollection | TemplateCollection;
-export interface Schema {
-    /**
-     * 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/
-     */
-    collections: Collection[];
-}
-export declare type TokenObject = {
-    id_token: string;
-    access_token?: string;
-    refresh_token?: string;
-};
-export interface Config<CMSCallback = undefined, FormifyCallback = undefined, DocumentCreatorCallback = undefined, Store = undefined> {
-    contentApiUrlOverride?: string;
-    admin?: {
-        auth?: {
-            /**
-             * If you wish to use the local auth provider, set this to true
-             *
-             * This will take precedence over the customAuth option (if set to true)
-             *
-             **/
-            useLocalAuth?: boolean;
-            /**
-             * If you are using a custom auth provider, set this to true
-             **/
-            customAuth?: boolean;
-            /**
-             *  Used for getting the token from the custom auth provider
-             *
-             * @returns {Promise<TokenObject | null>}
-             **/
-            getToken?: () => Promise<TokenObject | null>;
-            /**
-             *  Used to logout from the custom auth provider
-             *
-             **/
-            logout?: () => Promise<void>;
-            /**
-             *  Used for getting the user from the custom auth provider. If this returns a truthy value, the user will be logged in and the CMS will be enabled.
-             *
-             *  If this returns a falsy value, the user will be logged out and the CMS will be disabled.
-             *
-             **/
-            getUser?: () => Promise<any | null>;
-            /**
-             * Used to authenticate the user with the custom auth provider. This is called when the user clicks the login button.
-             *
-             **/
-            authenticate?: () => Promise<any | null>;
-            onLogin?: (args: {
-                token: TokenObject;
-            }) => Promise<void>;
-            onLogout?: () => Promise<void>;
-        };
-    };
-    /**
-     * The Schema is used to define the shape of the content.
-     *
-     * https://tina.io/docs/reference/schema/
-     */
-    schema: Schema;
-    /**
-     * The base branch to pull content from. Note that this is ignored for local development
-     */
-    branch: string | null;
-    /**
-     * Your clientId from  app.tina.io
-     */
-    clientId: string | null;
-    /**
-     * Your read only token from app.tina.io
-     */
-    token: string | null;
-    /**
-     * Configurations for the autogenerated GraphQL HTTP client
-     */
-    client?: {
-        /**
-         * Autogenerated queries will traverse references to a given depth
-         * @default 2
-         */
-        referenceDepth?: number;
-    };
-    /**
-     *
-     * Tina supports serving content from a separate Git repo. To enable this during local development, point
-     * this config at the root of the content repo.
-     *
-     * NOTE: Relative paths are fine to use here, but you should use an environment variable for this, as each developer on your team may have a different
-     * location to the path.
-     *
-     * ```ts
-     * localContentPath: process.env.REMOTE_ROOT_PATH // eg. '../../my-content-repo'
-     * ```
-     */
-    localContentPath?: string;
-    /**
-     * Tina is compiled as a single-page app and placed in the public directory
-     * of your application.
-     */
-    build: {
-        /**
-         * The folder where your application stores assets, eg. `"public"`
-         */
-        publicFolder: string;
-        /**
-         * The value specified here will determine the path when visiting the TinaCMS dashboard.
-         *
-         * Eg. `"admin"` will be viewable at `[your-development-url]/admin/index.html`
-         *
-         * Note that for most framworks you can omit the `index.html` portion, for Next.js see the [rewrites section](https://nextjs.org/docs/api-reference/next.config.js/rewrites)
-         */
-        outputFolder: string;
-        /**
-         *
-         *  the host option for the vite config. This is useful when trying to run tinacms dev in a docker container.
-         *
-         * See https://vitejs.dev/config/server-options.html#server-host for more details
-         */
-        host?: string | boolean;
-    };
-    media?: {
-        /**
-         * Load a media store like Cloudinary
-         *
-         * ```ts
-         * loadCustomStore = async () => {
-         *   const pack = await import("next-tinacms-cloudinary");
-         *   return pack.TinaCloudCloudinaryMediaStore;
-         * }
-         * ```
-         */
-        loadCustomStore: () => Promise<Store>;
-        tina?: never;
-    } | {
-        /**
-         * Use Git-backed assets for media, these values will
-         * [Learn more](https://tina.io/docs/reference/media/repo-based/)
-         */
-        tina: {
-            /**
-             * The folder where your application stores assets, eg. `"public"`
-             */
-            publicFolder: string;
-            /**
-             * The root folder for media managed by Tina. For example, `"uploads"`
-             * would store content in `"<my-public-folder>/uploads"`
-             */
-            mediaRoot: string;
-        };
-        loadCustomStore?: never;
-    };
-    /**
-     * Used to override the default Tina Cloud API URL
-     *
-     * [mostly for internal use only]
-     */
-    tinaioConfig?: {
-        assetsApiUrlOverride?: string;
-        frontendUrlOverride?: string;
-        identityApiUrlOverride?: string;
-        contentApiUrlOverride?: string;
-    };
-    cmsCallback?: CMSCallback;
-    formifyCallback?: FormifyCallback;
-    documentCreatorCallback?: DocumentCreatorCallback;
-}
-export declare type TinaCMSConfig<CMSCallback = undefined, FormifyCallback = undefined, DocumentCreatorCallback = undefined, Store = undefined> = Config<CMSCallback, FormifyCallback, DocumentCreatorCallback, Store>;
-export {};

package/dist/types.es.js

@@ -1 +0,0 @@
-

package/dist/types.js

@@ -1,5 +0,0 @@
-(function(factory) {
-  typeof define === "function" && define.amd ? define(factory) : factory();
-})(function() {
-  "use strict";
-});