Replies: 1 comment 1 reply
-
|
Sounds like there might be a regression, can you create an issue with an example that doesn’t work? Ideally something runnable or at least a full class definition. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I’ve been extending
ListNodeto add more list styles in my editor. Here’s a simplified version of my custom node:I register the replacement like this:
According to the [node replacement docs](https://lexical.dev/docs/concepts/node-replacement), I expected
CustomListNodeto inherit all transforms from the originalListNode.However, that’s no longer happening. Specifically, the transform
updateChildrenListItemValueis not called anymore, so when I press Enter to create a new list item, the nextListItemNodedoes not receive the updated value.I remember this used to work correctly about a year ago, but after updating to a recent Lexical version, it stopped working.
Right now I’m “cheating” with this workaround in
CustomListNode:With the recent changes around
$configandNodeState, what’s the correct way for myCustomListNodeto receive the transforms fromListNodeagain? Ideally, I’d like to keep my existing custom nodes and avoid migrating them to a completely new format if possible.Thanks! 🙏
Beta Was this translation helpful? Give feedback.
All reactions