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
Generalize Menu Logic #4284
Generalize Menu Logic #4284
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
LGTM, but I don't think we can merge this just yet as removing modules is a breaking change. Do you want to keep the old modules for now or you want to prioritize the next Lexical version? |
LGTM, but it might affect if anyone using old features. |
@tylerjbainbridge I don't know if you noticed but it broke the < .11 version because of this rename... what's the new guidance to use this API now? Are we expecting no backwards compatibility? |
Context--
Typeaheads were created and then some parts of the code were reused/adapted for the AutoEmbed menus. This led to a lot of extra code in the
LexicalTypeaheadMenuPlugin.tsx
.So in preparation for the upcoming
LexicalContextMenuPlugin
I've generalized the core menu logic intoLexicalMenus.ts
and separated theLexicalNodeMenuPlugin
that's used by Embeds into it's own file.Nothing functionally changed here. Things were just moved around/renamed to be more clear.
You can see this in action on the
new-context-menu-v1
branch which will have PRs coming soon.