@examind/block-types 0.1.18

package/types/lexical/LexicalNodeState.ts

@@ -0,0 +1,379 @@
+// THIS FILE IS AUTO-GENERATED
+// To regenerate, run: pnpm build (from the root of the project)
+
+// Type definitions based on Lexical
+// Original copyright: Meta Platforms, Inc. and affiliates.
+
+import type { LexicalNode } from './LexicalNode';
+import { NODE_STATE_KEY } from './LexicalConstants';
+/**
+ * The return value of {@link createState}, for use with
+ * {@link $getState} and {@link $setState}.
+ */
+export declare class StateConfig<K extends string, V> {
+    /** The string key used when serializing this state to JSON */
+    readonly key: K;
+    /** The parse function from the StateValueConfig passed to createState */
+    readonly parse: (value?: unknown) => V;
+    /**
+     * The unparse function from the StateValueConfig passed to createState,
+     * with a default that is simply a pass-through that assumes the value is
+     * JSON serializable.
+     */
+    readonly unparse: (value: V) => unknown;
+    /**
+     * An equality function from the StateValueConfig, with a default of
+     * Object.is.
+     */
+    readonly isEqual: (a: V, b: V) => boolean;
+    /**
+     * The result of `stateValueConfig.parse(undefined)`, which is computed only
+     * once and used as the default value. When the current value `isEqual` to
+     * the `defaultValue`, it will not be serialized to JSON.
+     */
+    readonly defaultValue: V;
+    constructor(key: K, stateValueConfig: StateValueConfig<V>);
+}
+/**
+ * For advanced use cases, using this type is not recommended unless
+ * it is required (due to TypeScript's lack of features like
+ * higher-kinded types).
+ *
+ * A {@link StateConfig} type with any key and any value that can be
+ * used in situations where the key and value type can not be known,
+ * such as in a generic constraint when working with a collection of
+ * StateConfig.
+ *
+ * {@link StateConfigKey} and {@link StateConfigValue} will be
+ * useful when this is used as a generic constraint.
+ */
+export type AnyStateConfig = StateConfig<any, any>;
+/**
+ * Get the value type (V) from a StateConfig
+ */
+export type StateConfigValue<S extends AnyStateConfig> = S extends StateConfig<infer _K, infer V> ? V : never;
+/**
+ * Get the key type (K) from a StateConfig
+ */
+export type StateConfigKey<S extends AnyStateConfig> = S extends StateConfig<infer K, infer _V> ? K : never;
+/**
+ * A value type, or an updater for that value type. For use with
+ * {@link $setState} or any user-defined wrappers around it.
+ */
+export type ValueOrUpdater<V> = V | ((prevValue: V) => V);
+/**
+ * Configure a value to be used with StateConfig.
+ *
+ * The value type should be inferred from the definition of parse.
+ *
+ * If the value type is not JSON serializable, then unparse must also be provided.
+ *
+ * Values should be treated as immutable, much like React.useState. Mutating
+ * stored values directly will cause unpredictable behavior, is not supported,
+ * and may trigger errors in the future.
+ *
+ * @example
+ * ```ts
+ * const numberOrNullState = createState('numberOrNull', {parse: (v) => typeof v === 'number' ? v : null});
+ * //    ^? State<'numberOrNull', StateValueConfig<number | null>>
+ * const numberState = createState('number', {parse: (v) => typeof v === 'number' ? v : 0});
+ * //    ^? State<'number', StateValueConfig<number>>
+ * ```
+ *
+ * Only the parse option is required, it is generally not useful to
+ * override `unparse` or `isEqual`. However, if you are using
+ * non-primitive types such as Array, Object, Date, or something
+ * more exotic then you would want to override this. In these
+ * cases you might want to reach for third party libraries.
+ *
+ * @example
+ * ```ts
+ * const isoDateState = createState('isoDate', {
+ *   parse: (v): null | Date => {
+ *     const date = typeof v === 'string' ? new Date(v) : null;
+ *     return date && !isNaN(date.valueOf()) ? date : null;
+ *   }
+ *   isEqual: (a, b) => a === b || (a && b && a.valueOf() === b.valueOf()),
+ *   unparse: (v) => v && v.toString()
+ * });
+ * ```
+ *
+ * You may find it easier to write a parse function using libraries like
+ * zod, valibot, ajv, Effect, TypeBox, etc. perhaps with a wrapper function.
+ */
+export interface StateValueConfig<V> {
+    /**
+     * This function must return a default value when called with undefined,
+     * otherwise it should parse the given JSON value to your type V. Note
+     * that it is not required to copy or clone the given value, you can
+     * pass it directly through if it matches the expected type.
+     *
+     * When you encounter an invalid value, it's up to you to decide
+     * as to whether to ignore it and return the default value,
+     * return some non-default error value, or throw an error.
+     *
+     * It is possible for V to include undefined, but if it does, then
+     * it should also be considered the default value since undefined
+     * can not be serialized to JSON so it is indistinguishable from the
+     * default.
+     *
+     * Similarly, if your V is a function, then usage of {@link $setState}
+     * must use an updater function because your type will be indistinguishable
+     * from an updater function.
+     */
+    parse: (jsonValue: unknown) => V;
+    /**
+     * This is optional and for advanced use cases only.
+     *
+     * You may specify a function that converts V back to JSON.
+     * This is mandatory when V is not a JSON serializable type.
+     */
+    unparse?: (parsed: V) => unknown;
+    /**
+     * This is optional and for advanced use cases only.
+     *
+     * Used to define the equality function so you can use an Array or Object
+     * as V and still omit default values from the exported JSON.
+     *
+     * The default is `Object.is`, but something like `fast-deep-equal` might be
+     * more appropriate for your use case.
+     */
+    isEqual?: (a: V, b: V) => boolean;
+}
+/**
+ * Create a StateConfig for the given string key and StateValueConfig.
+ *
+ * The key must be locally unique. In dev you will get a key collision error
+ * when you use two separate StateConfig on the same node with the same key.
+ *
+ * The returned StateConfig value should be used with {@link $getState} and
+ * {@link $setState}.
+ *
+ * @param key The key to use
+ * @param valueConfig Configuration for the value type
+ * @returns a StateConfig
+ */
+export declare function createState<K extends string, V>(key: K, valueConfig: StateValueConfig<V>): StateConfig<K, V>;
+/**
+ * Given two versions of a node and a stateConfig, compare their state values
+ * using `$getState(nodeVersion, stateConfig, 'direct')`.
+ * If the values are equal according to `stateConfig.isEqual`, return `null`,
+ * otherwise return `[value, prevValue]`.
+ *
+ * This is useful for implementing updateDOM. Note that the `'direct'`
+ * version argument is used for both nodes.
+ *
+ * @param node Any LexicalNode
+ * @param prevNode A previous version of node
+ * @param stateConfig The configuration of the state to read
+ * @returns `[value, prevValue]` if changed, otherwise `null`
+ */
+export declare function $getStateChange<T extends LexicalNode, K extends string, V>(node: T, prevNode: T, stateConfig: StateConfig<K, V>): null | [value: V, prevValue: V];
+/**
+ * The accessor for working with node state. This will read the value for the
+ * state on the given node, and will return `stateConfig.defaultValue` if the
+ * state has never been set on this node.
+ *
+ * The `version` parameter is optional and should generally be `'latest'`,
+ * consistent with the behavior of other node methods and functions,
+ * but for certain use cases such as `updateDOM` you may have a need to
+ * use `'direct'` to read the state from a previous version of the node.
+ *
+ * For very advanced use cases, you can expect that 'direct' does not
+ * require an editor state, just like directly accessing other properties
+ * of a node without an accessor (e.g. `textNode.__text`).
+ *
+ * @param node Any LexicalNode
+ * @param stateConfig The configuration of the state to read
+ * @param version The default value 'latest' will read the latest version of the node state, 'direct' will read the version that is stored on this LexicalNode which not reflect the version used in the current editor state
+ * @returns The current value from the state, or the default value provided by the configuration.
+ */
+export declare function $getState<K extends string, V>(node: LexicalNode, stateConfig: StateConfig<K, V>, version?: 'latest' | 'direct'): V;
+/**
+ * Set the state defined by stateConfig on node. Like with `React.useState`
+ * you may directly specify the value or use an updater function that will
+ * be called with the previous value of the state on that node (which will
+ * be the `stateConfig.defaultValue` if not set).
+ *
+ * When an updater function is used, the node will only be marked dirty if
+ * `stateConfig.isEqual(prevValue, value)` is false.
+ *
+ * @example
+ * ```ts
+ * const toggle = createState('toggle', {parse: Boolean});
+ * // set it direction
+ * $setState(node, counterState, true);
+ * // use an updater
+ * $setState(node, counterState, (prev) => !prev);
+ * ```
+ *
+ * @param node The LexicalNode to set the state on
+ * @param stateConfig The configuration for this state
+ * @param valueOrUpdater The value or updater function
+ * @returns node
+ */
+export declare function $setState<Node extends LexicalNode, K extends string, V>(node: Node, stateConfig: StateConfig<K, V>, valueOrUpdater: ValueOrUpdater<V>): Node;
+type KnownStateMap = Map<AnyStateConfig, unknown>;
+type UnknownStateRecord = Record<string, unknown>;
+type SharedConfigMap = Map<string, AnyStateConfig>;
+/**
+ * @internal
+ */
+export declare class NodeState<T extends LexicalNode> {
+    /**
+     * @internal
+     *
+     * Track the (versioned) node that this NodeState was created for, to
+     * facilitate copy-on-write for NodeState. When a LexicalNode is cloned,
+     * it will *reference* the NodeState from its prevNode. From the nextNode
+     * you can continue to read state without copying, but the first $setState
+     * will trigger a copy of the prevNode's NodeState with the node property
+     * updated.
+     */
+    readonly node: LexicalNode;
+    /**
+     * @internal
+     *
+     * State that has already been parsed in a get state, so it is safe. (can be returned with
+     * just a cast since the proof was given before).
+     *
+     * Note that it uses StateConfig, so in addition to (1) the CURRENT VALUE, it has access to
+     * (2) the State key (3) the DEFAULT VALUE and (4) the PARSE FUNCTION
+     */
+    readonly knownState: KnownStateMap;
+    /**
+     * @internal
+     *
+     * A copy of serializedNode[NODE_STATE_KEY] that is made when JSON is
+     * imported but has not been parsed yet.
+     *
+     * It stays here until a get state requires us to parse it, and since we
+     * then know the value is safe we move it to knownState and garbage collect
+     * it at the next version.
+     *
+     * Note that since only string keys are used here, we can only allow this
+     * state to pass-through on export or on the next version since there is
+     * no known value configuration. This pass-through is to support scenarios
+     * where multiple versions of the editor code are working in parallel so
+     * an old version of your code doesnt erase metadata that was
+     * set by a newer version of your code.
+     */
+    unknownState: undefined | UnknownStateRecord;
+    /**
+     * @internal
+     *
+     * This sharedConfigMap is preserved across all versions of a given node and
+     * remains writable. It is how keys are resolved to configuration.
+     */
+    readonly sharedConfigMap: SharedConfigMap;
+    /**
+     * @internal
+     *
+     * The count of known or unknown keys in this state, ignoring the
+     * intersection between the two sets.
+     */
+    size: number;
+    /**
+     * @internal
+     */
+    constructor(node: T, sharedConfigMap?: SharedConfigMap, unknownState?: undefined | UnknownStateRecord, knownState?: KnownStateMap, size?: number | undefined);
+    /** @internal */
+    getValue<K extends string, V>(stateConfig: StateConfig<K, V>): V;
+    /**
+     * @internal
+     *
+     * Used only for advanced use cases, such as collab. The intent here is to
+     * allow you to diff states with a more stable interface than the properties
+     * of this class.
+     */
+    getInternalState(): [
+        {
+            readonly [k in string]: unknown;
+        } | undefined,
+        ReadonlyMap<AnyStateConfig, unknown>
+    ];
+    /**
+     * Encode this NodeState to JSON in the format that its node expects.
+     * This returns `{[NODE_STATE_KEY]?: UnknownStateRecord}` rather than
+     * `UnknownStateRecord | undefined` so that we can support flattening
+     * specific entries in the future when nodes can declare what
+     * their required StateConfigs are.
+     */
+    toJSON(): {
+        [NODE_STATE_KEY]?: UnknownStateRecord;
+    };
+    /**
+     * @internal
+     *
+     * A NodeState is writable when the node to update matches
+     * the node associated with the NodeState. This basically
+     * mirrors how the EditorState NodeMap works, but in a
+     * bottom-up organization rather than a top-down organization.
+     *
+     * This allows us to implement the same "copy on write"
+     * pattern for state, without having the state version
+     * update every time the node version changes (e.g. when
+     * its parent or siblings change).
+     *
+     * @param node The node to associate with the state
+     * @returns The next writable state
+     */
+    getWritable(node: T): NodeState<T>;
+    /** @internal */
+    updateFromKnown<K extends string, V>(stateConfig: StateConfig<K, V>, value: V): void;
+    /**
+     * @internal
+     *
+     * This is intended for advanced use cases only, such
+     * as collab or dev tools.
+     *
+     * Update a single key value pair from unknown state,
+     * parsing it if the key is known to this node. This is
+     * basically like updateFromJSON, but the effect is
+     * isolated to a single entry.
+     *
+     * @param k The string key from an UnknownStateRecord
+     * @param v The unknown value from an UnknownStateRecord
+     */
+    updateFromUnknown(k: string, v: unknown): void;
+    /**
+     * @internal
+     *
+     * Reset all existing state to default or empty values,
+     * and perform any updates from the given unknownState.
+     *
+     * This is used when initializing a node's state from JSON,
+     * or when resetting a node's state from JSON.
+     *
+     * @param unknownState The new state in serialized form
+     */
+    updateFromJSON(unknownState: undefined | UnknownStateRecord): void;
+}
+/**
+ * @internal
+ *
+ * Only for direct use in very advanced integrations, such as lexical-yjs.
+ * Typically you would only use {@link createState}, {@link $getState}, and
+ * {@link $setState}. This is effectively the preamble for {@link $setState}.
+ */
+export declare function $getWritableNodeState<T extends LexicalNode>(node: T): NodeState<T>;
+/**
+ * @internal
+ *
+ * This is used to implement LexicalNode.updateFromJSON and is
+ * not intended to be exported from the package.
+ *
+ * @param node any LexicalNode
+ * @param unknownState undefined or a serialized State
+ * @returns A writable version of node, with the state set.
+ */
+export declare function $updateStateFromJSON<T extends LexicalNode>(node: T, unknownState: undefined | UnknownStateRecord): T;
+/**
+ * @internal
+ *
+ * Return true if the two nodes have equivalent NodeState, to be used
+ * to determine when TextNode are being merged, not a lot of use cases
+ * otherwise.
+ */
+export declare function $nodeStatesAreEquivalent<T extends LexicalNode>(a: undefined | NodeState<T>, b: undefined | NodeState<T>): boolean;
+export {};

package/types/lexical/LexicalNormalization.ts

@@ -0,0 +1,9 @@
+// THIS FILE IS AUTO-GENERATED
+// To regenerate, run: pnpm build (from the root of the project)
+
+// Type definitions based on Lexical
+// Original copyright: Meta Platforms, Inc. and affiliates.
+
+import type { RangeSelection, TextNode } from '.';
+export declare function $normalizeTextNode(textNode: TextNode): void;
+export declare function $normalizeSelection(selection: RangeSelection): RangeSelection;

package/types/lexical/LexicalReconciler.ts

@@ -0,0 +1,13 @@
+// THIS FILE IS AUTO-GENERATED
+// To regenerate, run: pnpm build (from the root of the project)
+
+// Type definitions based on Lexical
+// Original copyright: Meta Platforms, Inc. and affiliates.
+
+import type { LexicalEditor, MutatedNodes } from './LexicalEditor';
+import type { NodeKey } from './LexicalNode';
+import { EditorState } from './LexicalEditorState';
+type IntentionallyMarkedAsDirtyElement = boolean;
+export declare function $reconcileRoot(prevEditorState: EditorState, nextEditorState: EditorState, editor: LexicalEditor, dirtyType: 0 | 1 | 2, dirtyElements: Map<NodeKey, IntentionallyMarkedAsDirtyElement>, dirtyLeaves: Set<NodeKey>): MutatedNodes;
+export declare function storeDOMWithKey(key: NodeKey, dom: HTMLElement, editor: LexicalEditor): void;
+export {};