@payloadcms/richtext-lexical 3.71.0-canary.3 → 3.71.0-internal-debug.dea9d74

package/dist/features/typesClient.js

@@ -1,2 +1,62 @@
-export {};
+/**
+ * No dependencies => Features need to be sorted on the server first, then sent to client in right order
+ */ /**
+   * Return props, to make it easy to retrieve passed in props to this Feature for the client if anyone wants to
+   */ /** unSanitizedEditorConfig.features, but mapped */ // other resolved features, which have been loaded before this one. All features declared in 'dependencies' should be available here
+// unSanitized EditorConfig,
+/**
+ * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more "outside" functionality
+ */ // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+/**
+   * The text formats which are enabled by this feature.
+   */ /**
+   * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more "outside" functionality
+   */ // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more "outside" functionality
+// Determines at which position the Component will be added.
+// Determines at which position the Component will be added.
+/**
+   * Client Features can register their own providers, which will be nested below the EditorConfigProvider
+   */ /**
+   * Return props, to make it easy to retrieve passed in props to this Feature for the client if anyone wants to
+   */ /**
+     * Dynamic groups allow you to add different groups depending on the query string (so, the text after the slash).
+     * Thus, to re-calculate the available groups, this function will be called every time you type after the /.
+     *
+     * The groups provided by dynamicGroups will be merged with the static groups provided by the groups property.
+     */ /**
+     * Static array of groups together with the items in them. These will always be present.
+     * While typing after the /, they will be filtered by the query string and the keywords, key and display name of the items.
+     */ /**
+   * An opt-in, classic fixed toolbar which stays at the top of the editor
+   */ /**
+   * The default, floating toolbar which appears when you select text.
+   */ /**
+     * Array of toolbar groups / sections. Each section can contain multiple toolbar items.
+     */ export { }; /** The keys of all enabled features */  /**
+   * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more "outside" functionality
+   */  /**
+     * Dynamic groups allow you to add different groups depending on the query string (so, the text after the slash).
+     * Thus, to re-calculate the available groups, this function will be called every time you type after the /.
+     *
+     * The groups provided by dynamicGroups will be merged with the static groups provided by the groups property.
+     */  /**
+     * Static array of groups together with the items in them. These will always be present.
+     * While typing after the /, they will be filtered by the query string and the keywords, key and display name of the items.
+     */ 
+
 //# sourceMappingURL=typesClient.js.map

package/dist/features/typesClient.js.map

@@ -1 +1 @@
-{"version":3,"file":"typesClient.js","names":[],"sources":["../../src/features/typesClient.ts"],"sourcesContent":["import type {\n  Klass,\n  LexicalEditor,\n  LexicalNode,\n  LexicalNodeReplacement,\n  TextFormatType,\n} from 'lexical'\nimport type { ClientConfig, RichTextFieldClient } from 'payload'\nimport type React from 'react'\nimport type { JSX } from 'react'\n\nimport type { ClientEditorConfig } from '../lexical/config/types.js'\nimport type { SlashMenuGroup } from '../lexical/plugins/SlashMenu/LexicalTypeaheadMenuPlugin/types.js'\nimport type { Transformer } from '../packages/@lexical/markdown/index.js'\nimport type { FeatureClientSchemaMap } from '../types.js'\nimport type { ToolbarGroup } from './toolbars/types.js'\n\nexport type FeatureProviderProviderClient<\n  UnSanitizedClientFeatureProps = undefined,\n  ClientFeatureProps = UnSanitizedClientFeatureProps,\n> = (props: BaseClientFeatureProps<ClientFeatureProps>) => FeatureProviderClient<ClientFeatureProps>\n\n/**\n * No dependencies => Features need to be sorted on the server first, then sent to client in right order\n */\nexport type FeatureProviderClient<\n  UnSanitizedClientFeatureProps = undefined,\n  ClientFeatureProps = UnSanitizedClientFeatureProps,\n> = {\n  /**\n   * Return props, to make it easy to retrieve passed in props to this Feature for the client if anyone wants to\n   */\n  clientFeatureProps: BaseClientFeatureProps<UnSanitizedClientFeatureProps>\n  feature:\n    | ((props: {\n        config: ClientConfig\n        featureClientImportMap: Record<string, any>\n        featureClientSchemaMap: FeatureClientSchemaMap\n        /** unSanitizedEditorConfig.features, but mapped */\n        featureProviderMap: ClientFeatureProviderMap\n        field?: RichTextFieldClient\n        // other resolved features, which have been loaded before this one. All features declared in 'dependencies' should be available here\n        resolvedFeatures: ResolvedClientFeatureMap\n        schemaPath: string\n        // unSanitized EditorConfig,\n        unSanitizedEditorConfig: ClientEditorConfig\n      }) => ClientFeature<ClientFeatureProps>)\n    | ClientFeature<ClientFeatureProps>\n}\n\nexport type PluginComponent<ClientFeatureProps = any> = React.FC<{\n  clientProps: ClientFeatureProps\n}>\nexport type PluginComponentWithAnchor<ClientFeatureProps = any> = React.FC<{\n  anchorElem: HTMLElement\n  clientProps: ClientFeatureProps\n}>\n\n/**\n * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n */\nexport type SanitizedPlugin =\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponent\n      key: string\n      position: 'bottom' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponent\n      key: string\n      position: 'normal' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponent\n      key: string\n      position: 'top' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponentWithAnchor\n      desktopOnly?: boolean\n      key: string\n      position: 'floatingAnchorElem' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      Component: PluginComponent\n      key: string\n      position: 'aboveContainer'\n    }\n  | {\n      clientProps: any\n      Component: PluginComponent\n      key: string\n      position: 'belowContainer'\n    }\n\nexport type ClientFeature<ClientFeatureProps> = {\n  /**\n   * The text formats which are enabled by this feature.\n   */\n  enableFormats?: TextFormatType[]\n  markdownTransformers?: (\n    | ((props: {\n        allNodes: Array<Klass<LexicalNode> | LexicalNodeReplacement>\n        allTransformers: Transformer[]\n      }) => Transformer)\n    | Transformer\n  )[]\n  nodes?: Array<Klass<LexicalNode> | LexicalNodeReplacement>\n  /**\n   * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n   */\n  plugins?: Array<\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'aboveContainer' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'bottom' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'normal' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'top' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponentWithAnchor<ClientFeatureProps>\n        position: 'floatingAnchorElem' // Determines at which position the Component will be added.\n      }\n    | {\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'belowContainer' // Determines at which position the Component will be added.\n      }\n  >\n  /**\n   * Client Features can register their own providers, which will be nested below the EditorConfigProvider\n   */\n  providers?: Array<React.FC<{ children: JSX.Element }>>\n  /**\n   * Return props, to make it easy to retrieve passed in props to this Feature for the client if anyone wants to\n   */\n  sanitizedClientFeatureProps?: BaseClientFeatureProps<ClientFeatureProps>\n  slashMenu?: {\n    /**\n     * Dynamic groups allow you to add different groups depending on the query string (so, the text after the slash).\n     * Thus, to re-calculate the available groups, this function will be called every time you type after the /.\n     *\n     * The groups provided by dynamicGroups will be merged with the static groups provided by the groups property.\n     */\n    dynamicGroups?: ({\n      editor,\n      queryString,\n    }: {\n      editor: LexicalEditor\n      queryString: string\n    }) => SlashMenuGroup[]\n    /**\n     * Static array of groups together with the items in them. These will always be present.\n     * While typing after the /, they will be filtered by the query string and the keywords, key and display name of the items.\n     */\n    groups?: SlashMenuGroup[]\n  }\n  /**\n   * An opt-in, classic fixed toolbar which stays at the top of the editor\n   */\n  toolbarFixed?: {\n    groups: ToolbarGroup[]\n  }\n  /**\n   * The default, floating toolbar which appears when you select text.\n   */\n  toolbarInline?: {\n    /**\n     * Array of toolbar groups / sections. Each section can contain multiple toolbar items.\n     */\n    groups: ToolbarGroup[]\n  }\n}\n\nexport type BaseClientFeatureProps<ClientFeatureProps> = ClientFeatureProps extends undefined\n  ? {\n      featureKey: string\n      order: number\n    }\n  : {\n      featureKey: string\n      order: number\n    } & ClientFeatureProps\n\nexport type ResolvedClientFeature<ClientFeatureProps> = {\n  key: string\n  order: number\n} & ClientFeature<ClientFeatureProps>\n\nexport type ResolvedClientFeatureMap = Map<string, ResolvedClientFeature<any>>\n\nexport type ClientFeatureProviderMap = Map<string, FeatureProviderClient<any, any>>\n\nexport type SanitizedClientFeatures = {\n  /** The keys of all enabled features */\n  enabledFeatures: string[]\n  enabledFormats: TextFormatType[]\n  markdownTransformers: Transformer[]\n\n  /**\n   * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n   */\n  plugins?: Array<SanitizedPlugin>\n  slashMenu: {\n    /**\n     * Dynamic groups allow you to add different groups depending on the query string (so, the text after the slash).\n     * Thus, to re-calculate the available groups, this function will be called every time you type after the /.\n     *\n     * The groups provided by dynamicGroups will be merged with the static groups provided by the groups property.\n     */\n    dynamicGroups: Array<\n      ({ editor, queryString }: { editor: LexicalEditor; queryString: string }) => SlashMenuGroup[]\n    >\n    /**\n     * Static array of groups together with the items in them. These will always be present.\n     * While typing after the /, they will be filtered by the query string and the keywords, key and display name of the items.\n     */\n    groups: SlashMenuGroup[]\n  }\n} & Required<\n  Pick<ResolvedClientFeature<unknown>, 'nodes' | 'providers' | 'toolbarFixed' | 'toolbarInline'>\n>\n"],"mappings":"AAuNA","ignoreList":[]}
+{"version":3,"sources":["../../src/features/typesClient.ts"],"sourcesContent":["import type {\n  Klass,\n  LexicalEditor,\n  LexicalNode,\n  LexicalNodeReplacement,\n  TextFormatType,\n} from 'lexical'\nimport type { ClientConfig, RichTextFieldClient } from 'payload'\nimport type React from 'react'\nimport type { JSX } from 'react'\n\nimport type { ClientEditorConfig } from '../lexical/config/types.js'\nimport type { SlashMenuGroup } from '../lexical/plugins/SlashMenu/LexicalTypeaheadMenuPlugin/types.js'\nimport type { Transformer } from '../packages/@lexical/markdown/index.js'\nimport type { FeatureClientSchemaMap } from '../types.js'\nimport type { ToolbarGroup } from './toolbars/types.js'\n\nexport type FeatureProviderProviderClient<\n  UnSanitizedClientFeatureProps = undefined,\n  ClientFeatureProps = UnSanitizedClientFeatureProps,\n> = (props: BaseClientFeatureProps<ClientFeatureProps>) => FeatureProviderClient<ClientFeatureProps>\n\n/**\n * No dependencies => Features need to be sorted on the server first, then sent to client in right order\n */\nexport type FeatureProviderClient<\n  UnSanitizedClientFeatureProps = undefined,\n  ClientFeatureProps = UnSanitizedClientFeatureProps,\n> = {\n  /**\n   * Return props, to make it easy to retrieve passed in props to this Feature for the client if anyone wants to\n   */\n  clientFeatureProps: BaseClientFeatureProps<UnSanitizedClientFeatureProps>\n  feature:\n    | ((props: {\n        config: ClientConfig\n        featureClientImportMap: Record<string, any>\n        featureClientSchemaMap: FeatureClientSchemaMap\n        /** unSanitizedEditorConfig.features, but mapped */\n        featureProviderMap: ClientFeatureProviderMap\n        field?: RichTextFieldClient\n        // other resolved features, which have been loaded before this one. All features declared in 'dependencies' should be available here\n        resolvedFeatures: ResolvedClientFeatureMap\n        schemaPath: string\n        // unSanitized EditorConfig,\n        unSanitizedEditorConfig: ClientEditorConfig\n      }) => ClientFeature<ClientFeatureProps>)\n    | ClientFeature<ClientFeatureProps>\n}\n\nexport type PluginComponent<ClientFeatureProps = any> = React.FC<{\n  clientProps: ClientFeatureProps\n}>\nexport type PluginComponentWithAnchor<ClientFeatureProps = any> = React.FC<{\n  anchorElem: HTMLElement\n  clientProps: ClientFeatureProps\n}>\n\n/**\n * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n */\nexport type SanitizedPlugin =\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponent\n      key: string\n      position: 'bottom' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponent\n      key: string\n      position: 'normal' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponent\n      key: string\n      position: 'top' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n      Component: PluginComponentWithAnchor\n      desktopOnly?: boolean\n      key: string\n      position: 'floatingAnchorElem' // Determines at which position the Component will be added.\n    }\n  | {\n      clientProps: any\n      Component: PluginComponent\n      key: string\n      position: 'aboveContainer'\n    }\n  | {\n      clientProps: any\n      Component: PluginComponent\n      key: string\n      position: 'belowContainer'\n    }\n\nexport type ClientFeature<ClientFeatureProps> = {\n  /**\n   * The text formats which are enabled by this feature.\n   */\n  enableFormats?: TextFormatType[]\n  markdownTransformers?: (\n    | ((props: {\n        allNodes: Array<Klass<LexicalNode> | LexicalNodeReplacement>\n        allTransformers: Transformer[]\n      }) => Transformer)\n    | Transformer\n  )[]\n  nodes?: Array<Klass<LexicalNode> | LexicalNodeReplacement>\n  /**\n   * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n   */\n  plugins?: Array<\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'aboveContainer' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'bottom' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'normal' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'top' // Determines at which position the Component will be added.\n      }\n    | {\n        // plugins are anything which is not directly part of the editor. Like, creating a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n        Component: PluginComponentWithAnchor<ClientFeatureProps>\n        position: 'floatingAnchorElem' // Determines at which position the Component will be added.\n      }\n    | {\n        Component: PluginComponent<ClientFeatureProps>\n        position: 'belowContainer' // Determines at which position the Component will be added.\n      }\n  >\n  /**\n   * Client Features can register their own providers, which will be nested below the EditorConfigProvider\n   */\n  providers?: Array<React.FC<{ children: JSX.Element }>>\n  /**\n   * Return props, to make it easy to retrieve passed in props to this Feature for the client if anyone wants to\n   */\n  sanitizedClientFeatureProps?: BaseClientFeatureProps<ClientFeatureProps>\n  slashMenu?: {\n    /**\n     * Dynamic groups allow you to add different groups depending on the query string (so, the text after the slash).\n     * Thus, to re-calculate the available groups, this function will be called every time you type after the /.\n     *\n     * The groups provided by dynamicGroups will be merged with the static groups provided by the groups property.\n     */\n    dynamicGroups?: ({\n      editor,\n      queryString,\n    }: {\n      editor: LexicalEditor\n      queryString: string\n    }) => SlashMenuGroup[]\n    /**\n     * Static array of groups together with the items in them. These will always be present.\n     * While typing after the /, they will be filtered by the query string and the keywords, key and display name of the items.\n     */\n    groups?: SlashMenuGroup[]\n  }\n  /**\n   * An opt-in, classic fixed toolbar which stays at the top of the editor\n   */\n  toolbarFixed?: {\n    groups: ToolbarGroup[]\n  }\n  /**\n   * The default, floating toolbar which appears when you select text.\n   */\n  toolbarInline?: {\n    /**\n     * Array of toolbar groups / sections. Each section can contain multiple toolbar items.\n     */\n    groups: ToolbarGroup[]\n  }\n}\n\nexport type BaseClientFeatureProps<ClientFeatureProps> = ClientFeatureProps extends undefined\n  ? {\n      featureKey: string\n      order: number\n    }\n  : {\n      featureKey: string\n      order: number\n    } & ClientFeatureProps\n\nexport type ResolvedClientFeature<ClientFeatureProps> = {\n  key: string\n  order: number\n} & ClientFeature<ClientFeatureProps>\n\nexport type ResolvedClientFeatureMap = Map<string, ResolvedClientFeature<any>>\n\nexport type ClientFeatureProviderMap = Map<string, FeatureProviderClient<any, any>>\n\nexport type SanitizedClientFeatures = {\n  /** The keys of all enabled features */\n  enabledFeatures: string[]\n  enabledFormats: TextFormatType[]\n  markdownTransformers: Transformer[]\n\n  /**\n   * Plugins are react components which get added to the editor. You can use them to interact with lexical, e.g. to create a command which creates a node, or opens a modal, or some other more \"outside\" functionality\n   */\n  plugins?: Array<SanitizedPlugin>\n  slashMenu: {\n    /**\n     * Dynamic groups allow you to add different groups depending on the query string (so, the text after the slash).\n     * Thus, to re-calculate the available groups, this function will be called every time you type after the /.\n     *\n     * The groups provided by dynamicGroups will be merged with the static groups provided by the groups property.\n     */\n    dynamicGroups: Array<\n      ({ editor, queryString }: { editor: LexicalEditor; queryString: string }) => SlashMenuGroup[]\n    >\n    /**\n     * Static array of groups together with the items in them. These will always be present.\n     * While typing after the /, they will be filtered by the query string and the keywords, key and display name of the items.\n     */\n    groups: SlashMenuGroup[]\n  }\n} & Required<\n  Pick<ResolvedClientFeature<unknown>, 'nodes' | 'providers' | 'toolbarFixed' | 'toolbarInline'>\n>\n"],"names":[],"mappings":"AAsBA;;CAEC,GAKC;;GAEC,GAOK,iDAAiD,GAGjD,oIAAoI;AAGpI,4BAA4B;AAcpC;;CAEC,GAIK,6KAA6K;AAG1J,4DAA4D;AAI/E,6KAA6K;AAG1J,4DAA4D;AAI/E,6KAA6K;AAG7J,4DAA4D;AAI5E,6KAA6K;AAI9I,4DAA4D;AAgB/F;;GAEC,GAUD;;GAEC,GAGK,6KAA6K;AAElJ,4DAA4D;AAGvF,6KAA6K;AAE1J,4DAA4D;AAG/E,6KAA6K;AAE1J,4DAA4D;AAG/E,6KAA6K;AAE7J,4DAA4D;AAG5E,6KAA6K;AAE9I,4DAA4D;AAIhE,4DAA4D;AAG7F;;GAEC,GAED;;GAEC,GAGC;;;;;KAKC,GAQD;;;KAGC,GAGH;;GAEC,GAID;;GAEC,GAEC;;KAEC,GAwBL,WA4BC,CA3BC,qCAAqC,IAKrC;;GAEC,IAGC;;;;;KAKC,IAID;;;KAGC"}

package/dist/features/typesServer.js

@@ -1,2 +1,91 @@
-export {};
+/**
+   * This maps all population promises to the node type
+   */ /**
+   * fieldPromises are used for things like field hooks. They will be awaited before awaiting populationPromises
+   */ /** Keys of dependencies needed for this feature. These dependencies do not have to be loaded first, but they have to exist, otherwise an error will be thrown. */ /**  Keys of priority dependencies needed for this feature. These dependencies have to be loaded first AND have to exist, otherwise an error will be thrown. They will be available in the `feature` property. */ /** Keys of soft-dependencies needed for this feature. These are optional. Payload will attempt to load them before this feature, but doesn't throw an error if that's not possible. */ /**
+   * This is being called during the payload sanitization process
+   */ /** unSanitizedEditorConfig.features, but mapped */ // other resolved features, which have been loaded before this one. All features declared in 'dependencies' should be available here
+// unSanitized EditorConfig,
+/** Props which were passed into your feature will have to be passed here. This will allow them to be used / read in other places of the code, e.g. wherever you can use useEditorConfigContext */ /**
+   * Only available in `afterRead` hooks.
+   */ /**
+   * Only available in `afterRead` hooks.
+   */ /**
+   *  Only available in `afterRead` field hooks.
+   */ /** Boolean to denote if this hook is running against finding one, or finding many within the afterRead hook. */ /**
+   * The requested locale.
+   */ /**
+   * Only available in `afterRead` hooks.
+   */ /**
+   *  Only available in `afterRead` field hooks.
+   */ /**
+   * Only available in `afterRead` hooks.
+   */ /**
+   * Only available in `afterRead` hooks.
+   */ /**
+   * Only available in `afterRead` hooks.
+   */ /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */ /** The value of the node before any changes. Not available in afterRead hooks */ /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */ /** The value of the node before any changes. Not available in afterRead hooks */ /**
+   * Only available in `beforeChange` hooks.
+   */ /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */ /** The value of the node before any changes. Not available in afterRead hooks */ /**
+   * The original node with locales (not modified by any hooks).
+   */ /** The value of the node. */ /** The payload request object. It is mocked for Local API operations. */ // Define the node with hooks that use the node's exportJSON return type
+/**
+   * Allows you to define how a node can be serialized into different formats. Currently, only supports html.
+   * Markdown converters are defined in `markdownTransformers` and not here.
+   *
+   * @deprecated - will be removed in 4.0
+   */ /**
+     * @deprecated - will be removed in 4.0
+     */ /**
+   * If a node includes sub-fields (e.g. block and link nodes), passing those subFields here will make payload
+   * automatically populate, run hooks, and generate component import maps for them
+   */ /**
+     * Optional. If not provided, all possible sub-fields should be returned.
+     */ /**
+   * If a node includes sub-fields, the sub-fields data needs to be returned here, alongside `getSubFields` which returns their schema.
+   */ /**
+   * Allows you to run population logic when a node's data was requested from graphQL.
+   * While `getSubFields` and `getSubFieldsData` automatically handle populating sub-fields (since they run hooks on them), those are only populated in the Rest API.
+   * This is because the Rest API hooks do not have access to the 'depth' property provided by graphQL.
+   * In order for them to be populated correctly in graphQL, the population logic needs to be provided here.
+   */ /**
+   * Just like payload fields, you can provide hooks which are run for this specific node. These are called Node Hooks.
+   */ /**
+   * The actual lexical node needs to be provided here. This also supports [lexical node replacements](https://lexical.dev/docs/concepts/node-replacement).
+   */ /**
+   * This allows you to provide node validations, which are run when your document is being validated, alongside other payload fields.
+   * You can use it to throw a validation error for a specific node in case its data is incorrect.
+   */ /**
+   * This determines what props will be available on the Client.
+   */ /**
+   * Adds payload components to the importMap.
+   *
+   * If an object is provided, the imported components will automatically be made available to the client feature, keyed by the object's keys.
+   */ /**
+       * Current schema which will be modified by this function.
+       */ /**
+       * Allows you to define new top-level interfaces that can be re-used in the output schema.
+       */ /**
+   * Here you can provide i18n translations for your feature. These will only be available on the server and client.
+   *
+   * Translations here are automatically scoped to `lexical.featureKey.yourKey`
+   *
+   * @Example
+   * ```ts
+   * i18n: {
+   *   en: {
+   *     label: 'Horizontal Rule',
+   *   },
+   *   de: {
+   *     label: 'Trennlinie',
+   *   },
+   * }
+   * ```
+   * In order to access these translations, you would use `i18n.t('lexical:horizontalRule:label')`.
+   */ /** Props which were passed into your feature will have to be passed here. This will allow them to be used / read in other places of the code, e.g. wherever you can use useEditorConfigContext */ export { }; /**  The node types mapped to their converters */  /** The keys of all enabled features */  /**
+         * Current schema which will be modified by this function.
+         */  /**
+         * Allows you to define new top-level interfaces that can be re-used in the output schema.
+         */  /**  The node types mapped to their hooks */  /**  The node types mapped to their populationPromises */  /**  The node types mapped to their validations */ 
+
 //# sourceMappingURL=typesServer.js.map

package/dist/features/typesServer.js.map

@@ -1 +1 @@
-{"version":3,"file":"typesServer.js","names":[],"sources":["../../src/features/typesServer.ts"],"sourcesContent":["import type { GenericLanguages, I18n, I18nClient } from '@payloadcms/translations'\nimport type { JSONSchema4 } from 'json-schema'\nimport type {\n  Klass,\n  LexicalNode,\n  LexicalNodeReplacement,\n  SerializedEditorState,\n  SerializedLexicalNode,\n} from 'lexical'\nimport type {\n  Field,\n  FieldSchemaMap,\n  ImportMapGenerators,\n  JsonObject,\n  PayloadComponent,\n  PayloadRequest,\n  PopulateType,\n  ReplaceAny,\n  RequestContext,\n  RichTextField,\n  RichTextHooks,\n  SanitizedConfig,\n  TypedFallbackLocale,\n  ValidateOptions,\n  ValidationFieldError,\n} from 'payload'\n\nimport type { ServerEditorConfig } from '../lexical/config/types.js'\nimport type { Transformer } from '../packages/@lexical/markdown/index.js'\nimport type { LexicalRichTextField } from '../types.js'\nimport type { HTMLConverter } from './converters/lexicalToHtml_deprecated/converter/types.js'\nimport type { BaseClientFeatureProps } from './typesClient.js'\n\nexport type PopulationPromise<T extends SerializedLexicalNode = SerializedLexicalNode> = (args: {\n  context: RequestContext\n  currentDepth: number\n  depth: number\n  draft: boolean\n  /**\n   * This maps all population promises to the node type\n   */\n  editorPopulationPromises: Map<string, Array<PopulationPromise>>\n  field: LexicalRichTextField\n  /**\n   * fieldPromises are used for things like field hooks. They will be awaited before awaiting populationPromises\n   */\n  fieldPromises: Promise<void>[]\n  findMany: boolean\n  flattenLocales: boolean\n  node: T\n  overrideAccess: boolean\n  parentIsLocalized: boolean\n  populationPromises: Promise<void>[]\n  req: PayloadRequest\n  showHiddenFields: boolean\n  siblingDoc: JsonObject\n}) => void\n\nexport type NodeValidation<T extends SerializedLexicalNode = SerializedLexicalNode> = ({\n  node,\n  nodeValidations,\n  validation,\n}: {\n  node: T\n  nodeValidations: Map<string, Array<NodeValidation>>\n  validation: {\n    options: ValidateOptions<unknown, unknown, RichTextField, SerializedEditorState>\n    value: SerializedEditorState\n  }\n}) => Promise<string | true> | string | true\n\nexport type FeatureProviderProviderServer<\n  UnSanitizedServerFeatureProps = undefined,\n  ServerFeatureProps = UnSanitizedServerFeatureProps,\n  ClientFeatureProps = undefined,\n> = (\n  props?: UnSanitizedServerFeatureProps,\n) => FeatureProviderServer<UnSanitizedServerFeatureProps, ServerFeatureProps, ClientFeatureProps>\n\nexport type FeatureProviderServer<\n  UnSanitizedServerFeatureProps = undefined,\n  ServerFeatureProps = UnSanitizedServerFeatureProps,\n  ClientFeatureProps = undefined,\n> = {\n  /** Keys of dependencies needed for this feature. These dependencies do not have to be loaded first, but they have to exist, otherwise an error will be thrown. */\n  dependencies?: string[]\n  /**  Keys of priority dependencies needed for this feature. These dependencies have to be loaded first AND have to exist, otherwise an error will be thrown. They will be available in the `feature` property. */\n  dependenciesPriority?: string[]\n  /** Keys of soft-dependencies needed for this feature. These are optional. Payload will attempt to load them before this feature, but doesn't throw an error if that's not possible. */\n  dependenciesSoft?: string[]\n\n  /**\n   * This is being called during the payload sanitization process\n   */\n  feature:\n    | ((props: {\n        config: SanitizedConfig\n        /** unSanitizedEditorConfig.features, but mapped */\n        featureProviderMap: ServerFeatureProviderMap\n        isRoot?: boolean\n        parentIsLocalized: boolean\n        // other resolved features, which have been loaded before this one. All features declared in 'dependencies' should be available here\n        resolvedFeatures: ResolvedServerFeatureMap\n        // unSanitized EditorConfig,\n        unSanitizedEditorConfig: ServerEditorConfig\n      }) =>\n        | Promise<ServerFeature<ServerFeatureProps, ClientFeatureProps>>\n        | ServerFeature<ServerFeatureProps, ClientFeatureProps>)\n    | ServerFeature<ServerFeatureProps, ClientFeatureProps>\n  key: string\n  /** Props which were passed into your feature will have to be passed here. This will allow them to be used / read in other places of the code, e.g. wherever you can use useEditorConfigContext */\n  serverFeatureProps: UnSanitizedServerFeatureProps\n}\n\nexport type AfterReadNodeHookArgs<T extends SerializedLexicalNode> = {\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  currentDepth: number\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  depth: number\n  draft: boolean\n  fallbackLocale: TypedFallbackLocale\n  /**\n   *  Only available in `afterRead` field hooks.\n   */\n  fieldPromises: Promise<void>[]\n  /** Boolean to denote if this hook is running against finding one, or finding many within the afterRead hook. */\n  findMany: boolean\n  flattenLocales: boolean\n  /**\n   * The requested locale.\n   */\n  locale: string\n  overrideAccess: boolean\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  populateArg?: PopulateType\n  /**\n   *  Only available in `afterRead` field hooks.\n   */\n  populationPromises: Promise<void>[]\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  showHiddenFields: boolean\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  triggerAccessControl: boolean\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  triggerHooks: boolean\n}\n\nexport type AfterChangeNodeHookArgs<T extends SerializedLexicalNode> = {\n  /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */\n  operation: 'create' | 'delete' | 'read' | 'update'\n  /** The value of the node before any changes. Not available in afterRead hooks */\n  originalNode: T\n  previousNode: T\n}\nexport type BeforeValidateNodeHookArgs<T extends SerializedLexicalNode> = {\n  /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */\n  operation: 'create' | 'delete' | 'read' | 'update'\n  /** The value of the node before any changes. Not available in afterRead hooks */\n  originalNode: T\n  overrideAccess: boolean\n}\n\nexport type BeforeChangeNodeHookArgs<T extends SerializedLexicalNode> = {\n  /**\n   * Only available in `beforeChange` hooks.\n   */\n  errors: ValidationFieldError[]\n  mergeLocaleActions: (() => Promise<void> | void)[]\n  /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */\n  operation: 'create' | 'delete' | 'read' | 'update'\n  /** The value of the node before any changes. Not available in afterRead hooks */\n  originalNode: T\n  /**\n   * The original node with locales (not modified by any hooks).\n   */\n  originalNodeWithLocales?: T\n  previousNode: T\n\n  skipValidation: boolean\n}\n\nexport type BaseNodeHookArgs<T extends SerializedLexicalNode> = {\n  context: RequestContext\n  /** The value of the node. */\n  node: T\n  parentRichTextFieldPath: (number | string)[]\n  parentRichTextFieldSchemaPath: string[]\n  /** The payload request object. It is mocked for Local API operations. */\n  req: PayloadRequest\n}\n\nexport type AfterReadNodeHook<T extends SerializedLexicalNode> = (\n  args: AfterReadNodeHookArgs<T> & BaseNodeHookArgs<T>,\n) => Promise<T> | T\n\nexport type AfterChangeNodeHook<T extends SerializedLexicalNode> = (\n  args: AfterChangeNodeHookArgs<T> & BaseNodeHookArgs<T>,\n) => Promise<T> | T\n\nexport type BeforeChangeNodeHook<T extends SerializedLexicalNode> = (\n  args: BaseNodeHookArgs<T> & BeforeChangeNodeHookArgs<T>,\n) => Promise<T> | T\n\nexport type BeforeValidateNodeHook<T extends SerializedLexicalNode> = (\n  args: BaseNodeHookArgs<T> & BeforeValidateNodeHookArgs<T>,\n) => Promise<T> | T\n\n// Define the node with hooks that use the node's exportJSON return type\nexport type NodeWithHooks<T extends LexicalNode = any> = {\n  /**\n   * Allows you to define how a node can be serialized into different formats. Currently, only supports html.\n   * Markdown converters are defined in `markdownTransformers` and not here.\n   *\n   * @deprecated - will be removed in 4.0\n   */\n  converters?: {\n    /**\n     * @deprecated - will be removed in 4.0\n     */\n    html?: HTMLConverter<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>\n  }\n  /**\n   * If a node includes sub-fields (e.g. block and link nodes), passing those subFields here will make payload\n   * automatically populate, run hooks, and generate component import maps for them\n   */\n  getSubFields?: (args: {\n    /**\n     * Optional. If not provided, all possible sub-fields should be returned.\n     */\n    node?: ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>\n    req?: PayloadRequest\n  }) => Field[] | null\n  /**\n   * If a node includes sub-fields, the sub-fields data needs to be returned here, alongside `getSubFields` which returns their schema.\n   */\n  getSubFieldsData?: (args: {\n    node: ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>\n    req: PayloadRequest\n  }) => JsonObject\n  /**\n   * Allows you to run population logic when a node's data was requested from graphQL.\n   * While `getSubFields` and `getSubFieldsData` automatically handle populating sub-fields (since they run hooks on them), those are only populated in the Rest API.\n   * This is because the Rest API hooks do not have access to the 'depth' property provided by graphQL.\n   * In order for them to be populated correctly in graphQL, the population logic needs to be provided here.\n   */\n  graphQLPopulationPromises?: Array<\n    PopulationPromise<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>\n  >\n  /**\n   * Just like payload fields, you can provide hooks which are run for this specific node. These are called Node Hooks.\n   */\n  hooks?: {\n    afterChange?: Array<AfterChangeNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n    afterRead?: Array<AfterReadNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n    beforeChange?: Array<BeforeChangeNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n    beforeValidate?: Array<\n      BeforeValidateNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>\n    >\n  }\n  /**\n   * The actual lexical node needs to be provided here. This also supports [lexical node replacements](https://lexical.dev/docs/concepts/node-replacement).\n   */\n  node: Klass<T> | LexicalNodeReplacement\n  /**\n   * This allows you to provide node validations, which are run when your document is being validated, alongside other payload fields.\n   * You can use it to throw a validation error for a specific node in case its data is incorrect.\n   */\n  validations?: Array<NodeValidation<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n}\n\nexport type ServerFeature<ServerProps, ClientFeatureProps> = {\n  ClientFeature?: PayloadComponent<never, BaseClientFeatureProps<ClientFeatureProps>>\n  /**\n   * This determines what props will be available on the Client.\n   */\n  clientFeatureProps?: ClientFeatureProps\n  /**\n   * Adds payload components to the importMap.\n   *\n   * If an object is provided, the imported components will automatically be made available to the client feature, keyed by the object's keys.\n   */\n  componentImports?:\n    | {\n        [key: string]: PayloadComponent\n      }\n    | ImportMapGenerators[0]\n    | PayloadComponent[]\n  generatedTypes?: {\n    modifyOutputSchema: (args: {\n      collectionIDFieldTypes: { [key: string]: 'number' | 'string' }\n      config?: SanitizedConfig\n      /**\n       * Current schema which will be modified by this function.\n       */\n      currentSchema: JSONSchema4\n      field: LexicalRichTextField\n      i18n?: I18n\n      /**\n       * Allows you to define new top-level interfaces that can be re-used in the output schema.\n       */\n      interfaceNameDefinitions: Map<string, JSONSchema4>\n      isRequired: boolean\n    }) => JSONSchema4\n  }\n  generateSchemaMap?: (args: {\n    config: SanitizedConfig\n    field: RichTextField\n    i18n: I18nClient\n    props: ServerProps\n    schemaMap: FieldSchemaMap\n    schemaPath: string\n  }) => FieldSchemaMap | null\n  hooks?: RichTextHooks\n  /**\n   * Here you can provide i18n translations for your feature. These will only be available on the server and client.\n   *\n   * Translations here are automatically scoped to `lexical.featureKey.yourKey`\n   *\n   * @Example\n   * ```ts\n   * i18n: {\n   *   en: {\n   *     label: 'Horizontal Rule',\n   *   },\n   *   de: {\n   *     label: 'Trennlinie',\n   *   },\n   * }\n   * ```\n   * In order to access these translations, you would use `i18n.t('lexical:horizontalRule:label')`.\n   */\n  i18n?: Partial<GenericLanguages>\n  markdownTransformers?: (\n    | ((props: { allNodes: Array<NodeWithHooks>; allTransformers: Transformer[] }) => Transformer)\n    | Transformer\n  )[]\n  nodes?: Array<NodeWithHooks>\n\n  /** Props which were passed into your feature will have to be passed here. This will allow them to be used / read in other places of the code, e.g. wherever you can use useEditorConfigContext */\n  sanitizedServerFeatureProps?: ServerProps\n}\n\nexport type ResolvedServerFeature<ServerProps, ClientFeatureProps> = {\n  order: number\n} & Required<\n  Pick<\n    FeatureProviderServer<ServerProps, ClientFeatureProps>,\n    'dependencies' | 'dependenciesPriority' | 'dependenciesSoft' | 'key'\n  >\n> &\n  ServerFeature<ServerProps, ClientFeatureProps>\n\nexport type ResolvedServerFeatureMap = Map<string, ResolvedServerFeature<any, any>>\n\nexport type ServerFeatureProviderMap = Map<string, FeatureProviderServer<any, any, any>>\n\nexport type SanitizedServerFeatures = {\n  /**  The node types mapped to their converters */\n  converters: {\n    html: HTMLConverter[]\n  }\n  /** The keys of all enabled features */\n  enabledFeatures: string[]\n  generatedTypes: {\n    modifyOutputSchemas: Array<\n      (args: {\n        collectionIDFieldTypes: { [key: string]: 'number' | 'string' }\n        config?: SanitizedConfig\n        /**\n         * Current schema which will be modified by this function.\n         */\n        currentSchema: JSONSchema4\n        field: LexicalRichTextField\n        i18n?: I18n\n        /**\n         * Allows you to define new top-level interfaces that can be re-used in the output schema.\n         */\n        interfaceNameDefinitions: Map<string, JSONSchema4>\n        isRequired: boolean\n      }) => JSONSchema4\n    >\n  }\n  /**  The node types mapped to their hooks */\n\n  getSubFields?: Map<\n    string,\n    (args: { node: SerializedLexicalNode; req: PayloadRequest }) => Field[] | null\n  >\n  getSubFieldsData?: Map<\n    string,\n    (args: { node: SerializedLexicalNode; req: PayloadRequest }) => JsonObject\n  >\n  graphQLPopulationPromises: Map<string, Array<PopulationPromise>>\n  hooks: RichTextHooks\n  markdownTransformers: Transformer[]\n  nodeHooks?: {\n    afterChange?: Map<string, Array<AfterChangeNodeHook<SerializedLexicalNode>>>\n    afterRead?: Map<string, Array<AfterReadNodeHook<SerializedLexicalNode>>>\n    beforeChange?: Map<string, Array<BeforeChangeNodeHook<SerializedLexicalNode>>>\n    beforeValidate?: Map<string, Array<BeforeValidateNodeHook<SerializedLexicalNode>>>\n  } /**  The node types mapped to their populationPromises */\n  /**  The node types mapped to their validations */\n  validations: Map<string, Array<NodeValidation>>\n} & Required<Pick<ResolvedServerFeature<any, any>, 'i18n' | 'nodes'>>\n"],"mappings":"AAgXA","ignoreList":[]}
+{"version":3,"sources":["../../src/features/typesServer.ts"],"sourcesContent":["import type { GenericLanguages, I18n, I18nClient } from '@payloadcms/translations'\nimport type { JSONSchema4 } from 'json-schema'\nimport type {\n  Klass,\n  LexicalNode,\n  LexicalNodeReplacement,\n  SerializedEditorState,\n  SerializedLexicalNode,\n} from 'lexical'\nimport type {\n  Field,\n  FieldSchemaMap,\n  ImportMapGenerators,\n  JsonObject,\n  PayloadComponent,\n  PayloadRequest,\n  PopulateType,\n  ReplaceAny,\n  RequestContext,\n  RichTextField,\n  RichTextHooks,\n  SanitizedConfig,\n  TypedFallbackLocale,\n  ValidateOptions,\n  ValidationFieldError,\n} from 'payload'\n\nimport type { ServerEditorConfig } from '../lexical/config/types.js'\nimport type { Transformer } from '../packages/@lexical/markdown/index.js'\nimport type { LexicalRichTextField } from '../types.js'\nimport type { HTMLConverter } from './converters/lexicalToHtml_deprecated/converter/types.js'\nimport type { BaseClientFeatureProps } from './typesClient.js'\n\nexport type PopulationPromise<T extends SerializedLexicalNode = SerializedLexicalNode> = (args: {\n  context: RequestContext\n  currentDepth: number\n  depth: number\n  draft: boolean\n  /**\n   * This maps all population promises to the node type\n   */\n  editorPopulationPromises: Map<string, Array<PopulationPromise>>\n  field: LexicalRichTextField\n  /**\n   * fieldPromises are used for things like field hooks. They will be awaited before awaiting populationPromises\n   */\n  fieldPromises: Promise<void>[]\n  findMany: boolean\n  flattenLocales: boolean\n  node: T\n  overrideAccess: boolean\n  parentIsLocalized: boolean\n  populationPromises: Promise<void>[]\n  req: PayloadRequest\n  showHiddenFields: boolean\n  siblingDoc: JsonObject\n}) => void\n\nexport type NodeValidation<T extends SerializedLexicalNode = SerializedLexicalNode> = ({\n  node,\n  nodeValidations,\n  validation,\n}: {\n  node: T\n  nodeValidations: Map<string, Array<NodeValidation>>\n  validation: {\n    options: ValidateOptions<unknown, unknown, RichTextField, SerializedEditorState>\n    value: SerializedEditorState\n  }\n}) => Promise<string | true> | string | true\n\nexport type FeatureProviderProviderServer<\n  UnSanitizedServerFeatureProps = undefined,\n  ServerFeatureProps = UnSanitizedServerFeatureProps,\n  ClientFeatureProps = undefined,\n> = (\n  props?: UnSanitizedServerFeatureProps,\n) => FeatureProviderServer<UnSanitizedServerFeatureProps, ServerFeatureProps, ClientFeatureProps>\n\nexport type FeatureProviderServer<\n  UnSanitizedServerFeatureProps = undefined,\n  ServerFeatureProps = UnSanitizedServerFeatureProps,\n  ClientFeatureProps = undefined,\n> = {\n  /** Keys of dependencies needed for this feature. These dependencies do not have to be loaded first, but they have to exist, otherwise an error will be thrown. */\n  dependencies?: string[]\n  /**  Keys of priority dependencies needed for this feature. These dependencies have to be loaded first AND have to exist, otherwise an error will be thrown. They will be available in the `feature` property. */\n  dependenciesPriority?: string[]\n  /** Keys of soft-dependencies needed for this feature. These are optional. Payload will attempt to load them before this feature, but doesn't throw an error if that's not possible. */\n  dependenciesSoft?: string[]\n\n  /**\n   * This is being called during the payload sanitization process\n   */\n  feature:\n    | ((props: {\n        config: SanitizedConfig\n        /** unSanitizedEditorConfig.features, but mapped */\n        featureProviderMap: ServerFeatureProviderMap\n        isRoot?: boolean\n        parentIsLocalized: boolean\n        // other resolved features, which have been loaded before this one. All features declared in 'dependencies' should be available here\n        resolvedFeatures: ResolvedServerFeatureMap\n        // unSanitized EditorConfig,\n        unSanitizedEditorConfig: ServerEditorConfig\n      }) =>\n        | Promise<ServerFeature<ServerFeatureProps, ClientFeatureProps>>\n        | ServerFeature<ServerFeatureProps, ClientFeatureProps>)\n    | ServerFeature<ServerFeatureProps, ClientFeatureProps>\n  key: string\n  /** Props which were passed into your feature will have to be passed here. This will allow them to be used / read in other places of the code, e.g. wherever you can use useEditorConfigContext */\n  serverFeatureProps: UnSanitizedServerFeatureProps\n}\n\nexport type AfterReadNodeHookArgs<T extends SerializedLexicalNode> = {\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  currentDepth: number\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  depth: number\n  draft: boolean\n  fallbackLocale: TypedFallbackLocale\n  /**\n   *  Only available in `afterRead` field hooks.\n   */\n  fieldPromises: Promise<void>[]\n  /** Boolean to denote if this hook is running against finding one, or finding many within the afterRead hook. */\n  findMany: boolean\n  flattenLocales: boolean\n  /**\n   * The requested locale.\n   */\n  locale: string\n  overrideAccess: boolean\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  populateArg?: PopulateType\n  /**\n   *  Only available in `afterRead` field hooks.\n   */\n  populationPromises: Promise<void>[]\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  showHiddenFields: boolean\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  triggerAccessControl: boolean\n  /**\n   * Only available in `afterRead` hooks.\n   */\n  triggerHooks: boolean\n}\n\nexport type AfterChangeNodeHookArgs<T extends SerializedLexicalNode> = {\n  /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */\n  operation: 'create' | 'delete' | 'read' | 'update'\n  /** The value of the node before any changes. Not available in afterRead hooks */\n  originalNode: T\n  previousNode: T\n}\nexport type BeforeValidateNodeHookArgs<T extends SerializedLexicalNode> = {\n  /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */\n  operation: 'create' | 'delete' | 'read' | 'update'\n  /** The value of the node before any changes. Not available in afterRead hooks */\n  originalNode: T\n  overrideAccess: boolean\n}\n\nexport type BeforeChangeNodeHookArgs<T extends SerializedLexicalNode> = {\n  /**\n   * Only available in `beforeChange` hooks.\n   */\n  errors: ValidationFieldError[]\n  mergeLocaleActions: (() => Promise<void> | void)[]\n  /** A string relating to which operation the field type is currently executing within. Useful within beforeValidate, beforeChange, and afterChange hooks to differentiate between create and update operations. */\n  operation: 'create' | 'delete' | 'read' | 'update'\n  /** The value of the node before any changes. Not available in afterRead hooks */\n  originalNode: T\n  /**\n   * The original node with locales (not modified by any hooks).\n   */\n  originalNodeWithLocales?: T\n  previousNode: T\n\n  skipValidation: boolean\n}\n\nexport type BaseNodeHookArgs<T extends SerializedLexicalNode> = {\n  context: RequestContext\n  /** The value of the node. */\n  node: T\n  parentRichTextFieldPath: (number | string)[]\n  parentRichTextFieldSchemaPath: string[]\n  /** The payload request object. It is mocked for Local API operations. */\n  req: PayloadRequest\n}\n\nexport type AfterReadNodeHook<T extends SerializedLexicalNode> = (\n  args: AfterReadNodeHookArgs<T> & BaseNodeHookArgs<T>,\n) => Promise<T> | T\n\nexport type AfterChangeNodeHook<T extends SerializedLexicalNode> = (\n  args: AfterChangeNodeHookArgs<T> & BaseNodeHookArgs<T>,\n) => Promise<T> | T\n\nexport type BeforeChangeNodeHook<T extends SerializedLexicalNode> = (\n  args: BaseNodeHookArgs<T> & BeforeChangeNodeHookArgs<T>,\n) => Promise<T> | T\n\nexport type BeforeValidateNodeHook<T extends SerializedLexicalNode> = (\n  args: BaseNodeHookArgs<T> & BeforeValidateNodeHookArgs<T>,\n) => Promise<T> | T\n\n// Define the node with hooks that use the node's exportJSON return type\nexport type NodeWithHooks<T extends LexicalNode = any> = {\n  /**\n   * Allows you to define how a node can be serialized into different formats. Currently, only supports html.\n   * Markdown converters are defined in `markdownTransformers` and not here.\n   *\n   * @deprecated - will be removed in 4.0\n   */\n  converters?: {\n    /**\n     * @deprecated - will be removed in 4.0\n     */\n    html?: HTMLConverter<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>\n  }\n  /**\n   * If a node includes sub-fields (e.g. block and link nodes), passing those subFields here will make payload\n   * automatically populate, run hooks, and generate component import maps for them\n   */\n  getSubFields?: (args: {\n    /**\n     * Optional. If not provided, all possible sub-fields should be returned.\n     */\n    node?: ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>\n    req?: PayloadRequest\n  }) => Field[] | null\n  /**\n   * If a node includes sub-fields, the sub-fields data needs to be returned here, alongside `getSubFields` which returns their schema.\n   */\n  getSubFieldsData?: (args: {\n    node: ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>\n    req: PayloadRequest\n  }) => JsonObject\n  /**\n   * Allows you to run population logic when a node's data was requested from graphQL.\n   * While `getSubFields` and `getSubFieldsData` automatically handle populating sub-fields (since they run hooks on them), those are only populated in the Rest API.\n   * This is because the Rest API hooks do not have access to the 'depth' property provided by graphQL.\n   * In order for them to be populated correctly in graphQL, the population logic needs to be provided here.\n   */\n  graphQLPopulationPromises?: Array<\n    PopulationPromise<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>\n  >\n  /**\n   * Just like payload fields, you can provide hooks which are run for this specific node. These are called Node Hooks.\n   */\n  hooks?: {\n    afterChange?: Array<AfterChangeNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n    afterRead?: Array<AfterReadNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n    beforeChange?: Array<BeforeChangeNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n    beforeValidate?: Array<\n      BeforeValidateNodeHook<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>\n    >\n  }\n  /**\n   * The actual lexical node needs to be provided here. This also supports [lexical node replacements](https://lexical.dev/docs/concepts/node-replacement).\n   */\n  node: Klass<T> | LexicalNodeReplacement\n  /**\n   * This allows you to provide node validations, which are run when your document is being validated, alongside other payload fields.\n   * You can use it to throw a validation error for a specific node in case its data is incorrect.\n   */\n  validations?: Array<NodeValidation<ReturnType<ReplaceAny<T, LexicalNode>['exportJSON']>>>\n}\n\nexport type ServerFeature<ServerProps, ClientFeatureProps> = {\n  ClientFeature?: PayloadComponent<never, BaseClientFeatureProps<ClientFeatureProps>>\n  /**\n   * This determines what props will be available on the Client.\n   */\n  clientFeatureProps?: ClientFeatureProps\n  /**\n   * Adds payload components to the importMap.\n   *\n   * If an object is provided, the imported components will automatically be made available to the client feature, keyed by the object's keys.\n   */\n  componentImports?:\n    | {\n        [key: string]: PayloadComponent\n      }\n    | ImportMapGenerators[0]\n    | PayloadComponent[]\n  generatedTypes?: {\n    modifyOutputSchema: (args: {\n      collectionIDFieldTypes: { [key: string]: 'number' | 'string' }\n      config?: SanitizedConfig\n      /**\n       * Current schema which will be modified by this function.\n       */\n      currentSchema: JSONSchema4\n      field: LexicalRichTextField\n      i18n?: I18n\n      /**\n       * Allows you to define new top-level interfaces that can be re-used in the output schema.\n       */\n      interfaceNameDefinitions: Map<string, JSONSchema4>\n      isRequired: boolean\n    }) => JSONSchema4\n  }\n  generateSchemaMap?: (args: {\n    config: SanitizedConfig\n    field: RichTextField\n    i18n: I18nClient\n    props: ServerProps\n    schemaMap: FieldSchemaMap\n    schemaPath: string\n  }) => FieldSchemaMap | null\n  hooks?: RichTextHooks\n  /**\n   * Here you can provide i18n translations for your feature. These will only be available on the server and client.\n   *\n   * Translations here are automatically scoped to `lexical.featureKey.yourKey`\n   *\n   * @Example\n   * ```ts\n   * i18n: {\n   *   en: {\n   *     label: 'Horizontal Rule',\n   *   },\n   *   de: {\n   *     label: 'Trennlinie',\n   *   },\n   * }\n   * ```\n   * In order to access these translations, you would use `i18n.t('lexical:horizontalRule:label')`.\n   */\n  i18n?: Partial<GenericLanguages>\n  markdownTransformers?: (\n    | ((props: { allNodes: Array<NodeWithHooks>; allTransformers: Transformer[] }) => Transformer)\n    | Transformer\n  )[]\n  nodes?: Array<NodeWithHooks>\n\n  /** Props which were passed into your feature will have to be passed here. This will allow them to be used / read in other places of the code, e.g. wherever you can use useEditorConfigContext */\n  sanitizedServerFeatureProps?: ServerProps\n}\n\nexport type ResolvedServerFeature<ServerProps, ClientFeatureProps> = {\n  order: number\n} & Required<\n  Pick<\n    FeatureProviderServer<ServerProps, ClientFeatureProps>,\n    'dependencies' | 'dependenciesPriority' | 'dependenciesSoft' | 'key'\n  >\n> &\n  ServerFeature<ServerProps, ClientFeatureProps>\n\nexport type ResolvedServerFeatureMap = Map<string, ResolvedServerFeature<any, any>>\n\nexport type ServerFeatureProviderMap = Map<string, FeatureProviderServer<any, any, any>>\n\nexport type SanitizedServerFeatures = {\n  /**  The node types mapped to their converters */\n  converters: {\n    html: HTMLConverter[]\n  }\n  /** The keys of all enabled features */\n  enabledFeatures: string[]\n  generatedTypes: {\n    modifyOutputSchemas: Array<\n      (args: {\n        collectionIDFieldTypes: { [key: string]: 'number' | 'string' }\n        config?: SanitizedConfig\n        /**\n         * Current schema which will be modified by this function.\n         */\n        currentSchema: JSONSchema4\n        field: LexicalRichTextField\n        i18n?: I18n\n        /**\n         * Allows you to define new top-level interfaces that can be re-used in the output schema.\n         */\n        interfaceNameDefinitions: Map<string, JSONSchema4>\n        isRequired: boolean\n      }) => JSONSchema4\n    >\n  }\n  /**  The node types mapped to their hooks */\n\n  getSubFields?: Map<\n    string,\n    (args: { node: SerializedLexicalNode; req: PayloadRequest }) => Field[] | null\n  >\n  getSubFieldsData?: Map<\n    string,\n    (args: { node: SerializedLexicalNode; req: PayloadRequest }) => JsonObject\n  >\n  graphQLPopulationPromises: Map<string, Array<PopulationPromise>>\n  hooks: RichTextHooks\n  markdownTransformers: Transformer[]\n  nodeHooks?: {\n    afterChange?: Map<string, Array<AfterChangeNodeHook<SerializedLexicalNode>>>\n    afterRead?: Map<string, Array<AfterReadNodeHook<SerializedLexicalNode>>>\n    beforeChange?: Map<string, Array<BeforeChangeNodeHook<SerializedLexicalNode>>>\n    beforeValidate?: Map<string, Array<BeforeValidateNodeHook<SerializedLexicalNode>>>\n  } /**  The node types mapped to their populationPromises */\n  /**  The node types mapped to their validations */\n  validations: Map<string, Array<NodeValidation>>\n} & Required<Pick<ResolvedServerFeature<any, any>, 'i18n' | 'nodes'>>\n"],"names":[],"mappings":"AAsCE;;GAEC,GAGD;;GAEC,GAuCD,gKAAgK,GAEhK,+MAA+M,GAE/M,qLAAqL,GAGrL;;GAEC,GAIK,iDAAiD,GAIjD,oIAAoI;AAEpI,4BAA4B;AAOlC,gMAAgM,GAKhM;;GAEC,GAED;;GAEC,GAID;;GAEC,GAED,8GAA8G,GAG9G;;GAEC,GAGD;;GAEC,GAED;;GAEC,GAED;;GAEC,GAED;;GAEC,GAED;;GAEC,GAKD,gNAAgN,GAEhN,+EAA+E,GAK/E,gNAAgN,GAEhN,+EAA+E,GAM/E;;GAEC,GAGD,gNAAgN,GAEhN,+EAA+E,GAE/E;;GAEC,GASD,2BAA2B,GAI3B,uEAAuE,GAoBzE,wEAAwE;AAEtE;;;;;GAKC,GAEC;;KAEC,GAGH;;;GAGC,GAEC;;KAEC,GAIH;;GAEC,GAKD;;;;;GAKC,GAID;;GAEC,GASD;;GAEC,GAED;;;GAGC,GAMD;;GAEC,GAED;;;;GAIC,GAWG;;OAEC,GAID;;OAEC,GAcL;;;;;;;;;;;;;;;;;GAiBC,GAQD,gMAAgM,GAkBlM,WA+CqE,CA9CnE,+CAA+C,IAI/C,qCAAqC,IAO/B;;SAEC,IAID;;SAEC,IAMP,0CAA0C,IAkBxC,uDAAuD,IACzD,gDAAgD"}