@payloadcms/plugin-search 3.0.0-beta.134

v3.0.0-beta.134

on Node.js NPM

v3.0.0-beta.134 (2024-11-17)

🚀 Features

• support relationship writes using objects instead of IDs (#9253) (d21fca9)
• deprecates getPayloadHMR in favor of simpler getPayload (#9249) (31b32ef)
• richtext-lexical: allow replacing entire blocks with custom components (#9234) (63cc966)

⚡ Performance

• richtext-lexical: significantly reduce lexical rerendering and amount of network requests from blocks (#9255) (35917c6)

🐛 Bug Fixes

• proper casing for default root views (#9248) (ed21c1c)
• next: custom default root views (#9247) (c4269d2)
• ui: avoid calling getTableState from join field on create (#9256) (ef2475d)

⚠️ BREAKING CHANGES

• proper casing for default root views (#9248) (ed21c1c)

  Custom account and dashboard views now defined as lowercase in the
  config.

  import { buildConfig } from 'payload'
  
  const config = buildConfig({
    // ...
    admin: {
      components: {
        // ...
        views: {
          // ...
  -       Account: ...
  -       Dashboard: ...
  +       account: ...
  +       dashboard: ...
        },
      },
    },
  })

• richtext-lexical: significantly reduce lexical rerendering and amount of network requests from blocks (#9255) (35917c6)

  The field RSC now provides an initial state for all lexical blocks. This
  completely obliterates any flashes and lexical block loading states when
  loading or saving a document.

  This removes the feature.hooks.load and feature.hooks.save
  interfaces from custom lexical features, as they weren't used internally
  and added unnecessary, additional overhead.

  If you have custom features that use those, you can migrate to using
  normal payload hooks that run on the server instead of the client.

🤝 Contributors

• Sasha (@r1tsuu)
• Alessio Gravili (@AlessioGr)
• Jacob Fletcher (@jacobsfletch)
• Elliot DeNolf (@denolfe)
• James Mikrut (@jmikrut)