The best way to build a modern backend + admin UI. No black magic, all TypeScript, and fully open-source, Payload is both an app framework and a headless CMS.
MIT License
Bot releases are hidden (Show)
Published by denolfe 11 months ago
Most important: If you are updating @payloadcms/richtext-lexical
to v0.4.0 or higher, you will HAVE to update payload
to the latest version as well. If you don't update it, payload likely won't start up due to validation errors. It's generally good practice to upgrade packages prefixed with @payloadcms/
together with payload
and keep the versions in sync.
@payloadcms/richtext-slate
is not affected by this.
Every single property in the Feature
interface which accepts a React component now no longer accepts a React component, but a function which imports a React component instead. This is done to ensure no unnecessary client-only code is leaked to the server when importing Features on a server.
Here's an example migration:
Old:
import { BlockIcon } from '../../lexical/ui/icons/Block'
...
Icon: BlockIcon,
New:
// import { BlockIcon } from '../../lexical/ui/icons/Block' // <= Remove this import
...
Icon: () =>
// @ts-expect-error
import('../../lexical/ui/icons/Block').then((module) => module.BlockIcon),
Or alternatively, if you're using default exports instead of named exports:
// import BlockIcon from '../../lexical/ui/icons/Block' // <= Remove this import
...
Icon: () =>
// @ts-expect-error
import('../../lexical/ui/icons/Block'),
The types for SanitizedEditorConfig
and EditorConfig
have changed. Their respective lexical
property no longer expects the LexicalEditorConfig
. It now expects a function returning the LexicalEditorConfig
. You will have to adjust this if you adjusted that property anywhere, e.g. when initializing the lexical field editor property, or when initializing a new headless editor.
The following exports are now exported from the @payloadcms/richtext-lexical/components
subpath exports instead of @payloadcms/richtext-lexical
:
ToolbarButton
ToolbarDropdown
RichTextCell
RichTextField
defaultEditorLexicalConfig
You will have to adjust your imports, only if you import any of those properties in your project.
Published by denolfe 11 months ago
Published by denolfe 11 months ago
The SlashMenuGroup
and SlashMenuOption
classes have changed. If you have any custom lexical Features which are adding new slash menu entries, this will be a breaking change for you. If not, no action is required from your side.
Here are the breaking changes and how to migrate:
SlashMenuOption
's first argument is now used as a key
and not as a display name. Additionally, a new, optional displayName
property is added which will serve as the display name. Make sure your key
does not contain any spaces or special characters.title
property of SlashMenuGroup
has been replaced by a new, mandatory key
and an optional displayName
property. To migrate, you will have to remove the title
property and add a key
property instead - make sure you do not use spaces or special characters in the key
.Published by denolfe 11 months ago
Published by denolfe 11 months ago
Published by denolfe 11 months ago
this
as transpilers are not handling it well (#4145) (2c8d34d)Published by denolfe 12 months ago
Published by denolfe 12 months ago
Published by denolfe 12 months ago
Published by denolfe 12 months ago
Published by denolfe 12 months ago
Published by denolfe 12 months ago
Published by denolfe about 1 year ago
corrects versions collection casing (#3739)
updates req after file resize (#3754)
correctly renders focal point when crop is set to false (#3759)
account for many slug types in generate types (#3698)
handle graphQL: false on globals when building policy type (#3729)
renders id as fallback title in DeleteDocument (#3745)
properly handles hideAPIURL (#3721)
filesRequiredOnCreate typing, tests, linting (#3737)
webpack-bundler: corrects payload alias (#3769)
bundler-webpack: better node_modules resolution (#3744)
db-postgres: block and array inserts error (#3714)
live-preview: properly handles uploads and hasOne monomorphic relationships (#3719)
Published by denolfe about 1 year ago
Published by denolfe about 1 year ago
Published by denolfe about 1 year ago
Published by denolfe about 1 year ago
Published by denolfe about 1 year ago