-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Advanced Setup not working #264
Comments
Experiencing a similar issue with a fresh expo project. See repo here https://github.com/bambie1/test-rich-text
@17Amir17 any ideas what I could be doing wrong? |
I also struggled to get the advanced setup working based on the example. I did eventually get it working by making the "bridges" in AdvancedEditor match the "bridgeExtensions" in AdvancedRichText export const AdvancedEditor = () => {
const editor = useTenTap({
bridges: [SpoilerBridge, ...TenTapStartKit], // Add our custom spoiler bridge
});
return (
<EditorContent
editor={editor}
className={window.dynamicHeight ? "dynamic-height" : undefined}
/>
);
}; export const RichTextEditor = ({
initialContent: initialContent,
onChange,
}: RichTextEditorProps) => {
const editor = useEditorBridge({
customSource: editorHtml, // Custom web editor implementation (advanced setup)
autofocus: true,
initialContent: initialContent,
bridgeExtensions: [SpoilerBridge, ...TenTapStartKit], // Add our custom spoiler bridge
avoidIosKeyboard: true,
onChange: () => {
console.log("[RichTextEditor] Content changed");
editor.getHTML().then((html) => {
console.log("[RichTextEditor] New content:", html);
onChange?.(html);
});
},
}); |
Hey guys, |
thanks @victoriashih. Your suggestion helped, and I got it working now 🎉 I changed |
https://github.com/10play/10TapAdvancedExample Will update this in the docs |
I can't seem to get the advanced setup running. The toolbar never shows up and the wordcounter example never works.
at this point I think I'm probably doing something silly. Let me know if there's other information I can share.
The text was updated successfully, but these errors were encountered: