Not all fields of lexical editor block available in API

[south plinth]

I have an issue with a custom block type in the lexical editor. The block type contains richText fields that are just not present in the result returned from the API. Concretely, I have a cards module that has three rich text fields. Other fields of the card however are present in the response. Please look at the attached images of the post and the API response.

If you need the code, I already threw away a lot of what we had in the repo so that it is very close to a minimal sample. We have payload version 2.13.0 and @merry pendant/richtext-lexical version 0.10.0 in our package.json.

[brisk thorn]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Lexical Rich Text - Features overview
• Lexical Rich Text - Extending the lexical editor with Features - Features: The Building Blocks
• Rich Text Field - Editor-specific options
• Blocks Field - Block configs
• Form Builder Plugin - Fields - Field Overrides

Community-Help:

• form builder plugin: forms are created but aren't accessed to render on frontend

[worthy haven]

@cinder light could you take a look at this one when you have a minute?

[cinder light]

@south plinth you will have to remove localized: true from any block fields / sub fields within lexical blocks. Having that property set will make them vanish from the API response.

This was a bug and has been fixed in the latest 3.0 beta version (https://github.com/payloadcms/payload/pull/6489). If those same blocks/fields are shared & used in other places within payload, and you cannot remove localized: true, I recommend making a utility function which automatically strips localized: true from those fields

[south plinth]

Thank you for your answer, @cinder light !

This means in cases where I use the blocks only in a localized richText field, I can just omit the localized field and everything will work as expected? And the localisation will still work as the base richText field is localized, right?

[cinder light]

in cases where I use the blocks only in a localized richText field, I can just omit the localized field and everything will work as expected?
Exactly! Omit it from any field & sub-field
And the localisation will still work as the base richText field is localized, right?
Yep! If any parent is localized, in this case the richText field, the localization property of sub fields will not have any effect anyways (outside of this lexical bug where it breaks)

[south plinth]

Thank you so much! :) I'll give that a try

[brisk thorn]

Payload Bot

Thread Solved!

Glad your issue was resolved! :tada: If you want to help make payload better, please give us a :star: on GitHub and review us - It helps us a lot.

🌟 Star Us on GitHub

Click here to star us on GitHub

👍 Review Us

Click here to review us on G2

[vagrant wharf]

Hello