6a2e8149f1
Fixes https://github.com/payloadcms/payload/issues/13904 When using Postgres, saving a document can cause the editor to re-mount. If the document includes a blocks field, this leads to the editor incorrectly resetting its value to the previous state. The issue occurs because the editor is re-mounted without recalculating the initial Lexical state. This re-mounting behavior is caused by how Postgres handles JSON storage: - With `jsonb` columns, unlike `json` columns, object key order is not guaranteed. - As a result, saving and reloading the Lexical editor state shifts key order, causing `JSON.stringify()` comparisons to fail. ## Solution To fix this, we now compare the incoming and previous editor state in a way that ignores key order. Specifically, we switched from `JSON.stringify()` to `dequal` for deep equality checks. ## Notes - This code only runs when external changes occur (e.g. after saving a document or when custom code modifies form fields). - Because this check is infrequent, performance impact is negligible. --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1211488746010087
Payload Lexical Rich Text Editor
Lexical Rich Text Editor for Payload.
Installation
npm install @payloadcms/richtext-lexical
Usage
import { buildConfig } from 'payload'
import { lexicalEditor } from '@payloadcms/richtext-lexical'
export default buildConfig({
editor: lexicalEditor({}),
// ...rest of config
})
More detailed usage can be found in the Payload Docs.