-
Notifications
You must be signed in to change notification settings - Fork 3.2k
fix: previousValue from hooks should be populated within lexical blocks #14856
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
base: main
Are you sure you want to change the base?
Conversation
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
| editor: lexicalEditor({ | ||
| features: ({ defaultFeatures }) => [ | ||
| ...defaultFeatures, | ||
| BlocksFeature({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Jessica,
Thank you for raising this PR. Please can we add a test for the LinkFeature, where a custom block can be configured and ensure the tests pass correctly for such instances.
What?
Updates the
previousValuedata sent to theafterChangehook to accomodate lexical nested paths.Why?
Currently the
afterChangehook uses the previousDoc:However, with fields from within Lexical, the data on the full
previousDochas a complex nesting structure. In this case, we should be using thepreviousSiblingDocto only return the sibling data and easily de-structure the data.How?
Checks if sibling data exists, and uses it if it does:
Reported by client.
Related PR: #14582