npm @payloadcms/plugin-search 3.0.0-beta.46
v3.0.0-beta.46

latest releases: 3.0.0-beta.130, 3.0.0-canary.6b9e4be, 3.0.0-beta.129...
5 months ago

v3.0.0-beta.46 (2024-06-12)

Features

  • diff generated types before write (#6749) (be0462d)
  • richtext-lexical: sub-field hooks and localization support (#6591) (4e12705)

Bug Fixes

BREAKING CHANGES

  • richtext-lexical: sub-field hooks and localization support (#6591) (4e12705)

BREAKING

  • Our internal field hook methods now have new required schemaPath and
    path props. This affects the following functions, if you are using
    those: afterChangeTraverseFields, afterReadTraverseFields,
    beforeChangeTraverseFields, beforeValidateTraverseFields,
    afterReadPromise
  • The afterChange field hook's value is now the value AFTER the
    previous hooks were run. Previously, this was the original value, which
    I believe is a bug
  • Only relevant if you have built your own richText adapter: the
    richText adapter populationPromises property has been renamed to
    graphQLPopulationPromises and is now only run for graphQL. Previously,
    it was run for graphQL AND the rest API. To migrate, use
    hooks.afterRead to run population for the rest API
  • Only relevant if you have built your own lexical features: The
    populationPromises server feature property has been renamed to
    graphQLPopulationPromises and is now only run for graphQL. Previously,
    it was run for graphQL AND the rest API. To migrate, use
    hooks.afterRead to run population for the rest API
  • Serialized lexical link and upload nodes now have a new id property.
    While not breaking, localization / hooks will not work for their fields
    until you have migrated to that. Re-saving the old document on the new
    version will automatically add the id property for you. You will also
    get a bunch of console logs for every lexical node which is not migrated

Contributors

Don't miss a new plugin-search release

NewReleases is sending notifications on new releases.