Enforcing strict TipTap extensions (nodes/marks) in v4 RichEditor

[vvb13a]

Package

Form builder

Package Version

v4.11.7

How can we help you?

Hi everyone,

I am currently using Filament v3 alongside a custom fork of the awcodes/filament-tiptap-editor plugin. With Filament v4 introducing TipTap natively as the default engine for RichEditor, I am looking to migrate to the native solution. However, I have run into a potential roadblock.

Is there a way to strictly enforce which extensions (nodes and marks) are registered with the TipTap editor at the JavaScript/client-side instantiation level in v4?

One of the key benefits of TipTap is its strict schema enforcement. For example, if the Bold node/mark is not registered, any pasted content containing bold text will have that formatting stripped automatically. This ensures consistency between what the user sees in the editor and what is eventually saved or sanitized on the server.

In my testing with the v4 RichEditor, disabling a toolbar button does not seem to prevent the underlying node/mark from being registered in the TipTap instance (meaning pasted formatted text is still accepted). I haven't found a way to strictly limit the registered extensions or schema.

Is there an existing configuration or method to achieve this level of control in v4, or is the schema currently fixed?