Feature Request: Configurable tokenizer/regex for createInlineMarkdownSpec (mentions not in [...]) #7098
weilinzung
started this conversation in
Feature Requests
Replies: 1 comment
-
|
Also, renderHTML?: ((this: {
name: string;
options: Options;
storage: Storage;
parent: ParentConfig<NodeConfig<Options, Storage>>['renderHTML'];
editor?: Editor;
}, props: {
node: Node$1;
HTMLAttributes: Record<string, any>;
}) => DOMOutputSpec) | null; |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Description
Currently, createInlineMarkdownSpec assumes fixed token patterns (e.g., [[mention]]) and doesn’t allow customizing how inline tokens like mentions are parsed. In our app, mentions are stored simply as @username, so the default tokenizer doesn’t recognize them.
We’d like the ability to pass a custom regex or tokenizer to createInlineMarkdownSpec, so developers can define how inline elements (mentions, tags, etc.) are detected and converted into nodes/marks.
https://github.com/ueberdosis/tiptap/blob/f1fc4696a69214bc9165165fe5cf8003fdb2f96a/packages/core/src/utilities/markdown/createInlineMarkdownSpec.ts
Use Case
Type
Other
Beta Was this translation helpful? Give feedback.
All reactions