Repository navigation
[lexical] Bug Fix: LexicalNode.getType() fallback to $config protocol - #7671
Merged
Merged
Conversation
etrepum
requested review from
Fetz,
Sahejkm,
acywatson,
fantactuka,
ivailop7,
lilshady,
potatowagon,
takuyakanbr and
zurfyx
as code owners
July 3, 2025 20:44
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
zurfyx
approved these changes
Jul 3, 2025
This branch was successfully deployed
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.
Description
Follow-up to #7258
The
$configprotocol initially assumed that no code was callingNode.getType()before the Node was used in an editor, but there is a use case with plug-ins. This changes the stub implementation ofLexicalNode.getType()to support the$configprotocol directly.Test plan
Before
Calling
Node.getType()on a node using the$configprotocol will throw if it has not first been registered with an editorAfter
Calling
Node.getType()is safe at all times