LexicalMenu rewrite with Floating UI#7623
Closed
ivailop7 wants to merge 8 commits intofacebook:mainfrom
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
6f57532 to
49293e7
Compare
10d5728 to
dbebbf5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking Change for LexicalMenu users
This one turned out much harder than I expected, due to the dual focus that needed to be maintained:
this was achieved by wrapping the App with FloatingTree and using the virtual logic of Floating UI for cases like this. More context here
To Do:
Migration plan for the Release notes:
<FloatingTree>component from 'floating-ui/react'