feat: Full Markdown AI integration

[supersimple33]

Addresses #4040 now with ui movement.

Checklist

• yarn typecheck
• yarn lint:fix
• yarn test
• yarn brl
• yarn changeset
• ui changelog

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

🦋 Changeset detected

Latest commit: 834b0b9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@udecode/plate-ai	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
plate	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 15, 2025 10:19pm

[supersimple33]

@zbeyens @felixfeng33 Okay I saw what you guys meant earlier with the ai-menu not properly moving itself as needed and blinding the ai content. I drafted up this PR which includes my previous fix but would in theory update the useRef of the anchorNode once that content has been set. Unfortunately I seem unable to get any father as I would expect my code to work but my toDOMNode call inside of ai-menu.tsx is failing unexpectedly. It seems that I can get a key for the WeakMap fine but that key must be stored at a new memory address and thus not the real one. I was wondering if you guys had any ideas as to why this is happening?

[supersimple33]

As solution could be to use the id supplying plugin and then use a standard call to find the node with the correct id but I was trying to avoid that.

[supersimple33]

I also found a one line thing where some braces were missing in a call that should have expanded an object and made #4070 since this is still in development.

[supersimple33]

Ok turns out I was being a little bit silly and didn't realize I wasn't giving the DOM enough time to update so the WeakMap literally couldn't contain values which hadn't been created yet. Anyways the latest commit has a fix for that however I am not super confident the way I made updateAnchorElement follows best practices so please let me know there. @zbeyens @felixfeng33

[supersimple33]

Also heres a video of the changes.

Screen.Recording.2025-02-11.at.11.18.37.AM.mov

[zbeyens]

Can you undo/redo the AI changes?

[felixfeng33]

I see the menu sometimes appears in the top left corner. And in the ideal circumstances we shouldn't see the md marks after this line is done

[supersimple33]

Can you undo/redo the AI changes?

@zbeyens Yes all ai changes are undone or redone with a single hit of the button.

[supersimple33]

@felixfeng33 Ok looks like I left in a debugging thing but I took it out and that should stop the bar from going to the top left. Also, I was trying to minimize the number of calls to the markdown deserializer and was just keeping it to the last call in the end. But I could switch it to run after every chunk I just figured that may be expensive for little benefit.

[felixfeng33]

@supersimple33 Yes call deserializer in every chunk will make all things very tricky, but I think we should take a try.

[supersimple33]

@felixfeng33 Ok so I tried a quick change to clear the aiNodes and reformat them every time but the trouble there is because of the speed at which chunks are loaded most of the time you fail to actually see what the editor is writing except for brief moments until the end when no more chunks are coming. I'm willing to investigate further but could we first get this merged and then I work on having it be updated continuously?

[zbeyens]

This is a nice fix but it introduces a regression so we can't merge this right now. In the meantime you could use configure(() => ({ useHooks: ... }) in your plugin