Open
Description
Describe the Bug
When implementing the BlocksNode component in Lexical Blocks, I intend to use UUIDs for block IDs. However, despite attempting to integrate UUIDs, the system continues to generate and use hex strings as IDs.
Expected behavior: The system should generate and assign a UUID for each new block created within the BlocksNode component.
Current behavior: The blocks still receive hex string IDs, contrary to the expected UUID format. This occurs even though I have attempted to override the default ID generation method.
Link to the code that reproduces this issue
https://github.com/himanshu-ntml/extend-table-issue
Reproduction Steps
- git clone
- npm i
- set db connection
- npm run dev
Which area(s) are affected? (Select all that apply)
plugin: richtext-lexical
Environment Info
Binaries:
Node: 22.11.0
npm: 11.0.0
Yarn: 1.22.22
pnpm: 9.12.3
Relevant Packages:
payload: 3.9.0
next: 15.1.0
@payloadcms/db-postgres: 3.9.0
@payloadcms/email-nodemailer: 3.9.0
@payloadcms/graphql: 3.9.0
@payloadcms/next/utilities: 3.9.0
@payloadcms/payload-cloud: 3.9.0
@payloadcms/richtext-lexical: 3.9.0
@payloadcms/translations: 3.9.0
@payloadcms/ui/shared: 3.9.0
react: 19.0.0
react-dom: 19.0.0
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.2.0: Fri Dec 6 19:01:59 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6000
Available memory (MB): 65536
Available CPU cores: 10