payload 2.3.0

Release v2.3.0

on Node.js NPM

2.3.0 (2023-11-30)

Features

• add serbian (latin and cyrillic) translations (#4268) (40c8909)
• db-mongodb: search for migrations dir intelligently (530c825)
• db-postgres: search for migrations dir intelligently (308979f)
• live-preview: batches api requests (#4315) (d49bb43)
• relationship sortOptions property (#4301) (224cddd)
• support migrations with js files (2122242)
• support OAuth 2.0 format Authorization: Bearer tokens in headers (c1eb9d1)
• useDocumentEvents (#4284) (9bb7a88)

Bug Fixes

• db-postgres: allow for nested block fields to be queried (#4237) (cd07873)
• db-postgres: error saving nested arrays with versions (#4302) (3514bfb)
• duplicate documents with required localized fields (#4236) (9da9b1f)
• incorrect key property in Tabs field component (#4311) (3502ce7), closes #4282
• live-preview-react: removes payload from peer deps (7e1052f)
• live-preview: compounds merge results (#4306) (381c158)
• live-preview: property resets rte nodes (#4313) (66679fb)
• live-preview: re-populates externally updated relationships (#4287) (57fc211)
• live-preview: removes payload from peer deps (b4af95f)
• properly exports useDocumentsEvents hook (#4314) (5420963)
• properly sets tabs key in fieldSchemaToJSON (#4317) (9cc88bb)
• richtext-lexical: HTML Converter field not working inside of tabs (#4293) (5bf6493)
• richtext-lexical: re-use payload population logic to fix population-related issues (#4291) (094d02c)
• richtext-slate: add use client to top of tsx files importing from payload core (#4312) (d4f28b1)

BREAKING CHANGES

⚠️ @payloadcms/richtext-lexical

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:

1. The 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.
2. The 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.
3. Additionally, if you have custom styles targeting elements inside of slash or floating-select-toolbar menus, you will have to adjust those too, as the CSS classes changed

This is an example of performing these updates