[lexical-react] Fix: Use explicit key attr in NodeContextMenuPlugin#7803
Merged
ivailop7 merged 1 commit intofacebook:mainfrom Sep 9, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ivailop7
approved these changes
Sep 9, 2025
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
2 participants
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.
Description
Explicitly specify the key attribute in the implementation of NodeContextMenuPlugin instead of relying on a spread. This seems to cause a problem with the way next.js handles jsx. I was expecting it to show up when using React 19 but it didn't seem to complain in the draft #7802 (before I added the commit for this fix).
Closes #7801
Test plan
I think this requires next.js to reproduce so it's hard in our current test environment