Skip to content
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

Add missing usages of $applyNodeReplacement #3592

Merged
merged 1 commit into from
Dec 19, 2022

Conversation

thegreatercurve
Copy link
Contributor

No description provided.

@vercel
Copy link

vercel bot commented Dec 19, 2022

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

Name Status Preview Comments Updated
lexical ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Dec 19, 2022 at 6:07PM (UTC)
lexical-playground ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Dec 19, 2022 at 6:07PM (UTC)

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Dec 19, 2022
@thegreatercurve thegreatercurve changed the title Add missing usages of $applyReplacementNode Add missing usages of $applyNodeReplacement Dec 19, 2022
@thegreatercurve thegreatercurve force-pushed the bug/missing-apply-node-replacements branch from cb82b06 to 30ef5a8 Compare December 19, 2022 10:44
@thegreatercurve thegreatercurve force-pushed the bug/missing-apply-node-replacements branch from 30ef5a8 to eaa5f54 Compare December 19, 2022 10:46
@thegreatercurve thegreatercurve marked this pull request as ready for review December 19, 2022 10:46
@thegreatercurve thegreatercurve changed the title Add missing usages of $applyNodeReplacement Add missing usages of $applyNodeReplacement Dec 19, 2022
@thegreatercurve thegreatercurve force-pushed the bug/missing-apply-node-replacements branch from a2d1a1f to 9d7c62d Compare December 19, 2022 15:03
Copy link
Contributor

@acywatson acywatson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally you don't need to add $applyNodeReplacement to your subclasses unless you plan to expose them as a library, which I think is probably rare in userland. I would say let's not put this in every creator on the playground for people to just copy and paste everywhere. The problem this is solving is allowing customization of core node behavior without changing the core library itself. The concept is not necessarily useful or applicable in places like TweetNode, where we don't even expose the node.

@thegreatercurve
Copy link
Contributor Author

@acywatson Fair point. I've just added it in to the exported nodes now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants