Provide a JsonCompatible adapter for RichTextValue objects

[erral]

Fixes #1583

[mister-roboto]

@erral thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

[netlify]

✅ Deploy Preview for plone-restapi canceled.

Name	Link
🔨 Latest commit	29d679a
🔍 Latest deploy log	https://app.netlify.com/sites/plone-restapi/deploys/63ea6980242d520008290caa

[netlify]

✅ Deploy Preview for plone-restapi canceled.

Name	Link
🔨 Latest commit	127d596
🔍 Latest deploy log	https://app.netlify.com/sites/plone-restapi/deploys/63ea693863815c000827eb05

[jensens]

Your solution provides only the rendered safe-HTML. But what if we want to get the raw data from the field, for an editor or alike? This could be any content type as raw, i.e. markdown. I do not think this implementation is enough. I would expect something like a dict with output, raw and its configured types, i.e something like:

{
    "output": {
        "data": "<p>foo<p>",
        "type": "text/safe-html",
    "raw": {
        "data": "foo",
        "data": "text/plain",
}

[erral]

This is the initial draft.

I first checked what happens when you add a simple HTML as a default value of the RichText field. I will test further with some other values.

[jensens]

OK! Since this is not a draft PR nor labels were applied, my understanding was like it is ready for review.

[erral]

I have updated the PR to implement the more generic fallback mechanism discussed in issue #1583.

Instead of adding a new global adapter, I improved the json_compatible helper to fall back to the Plone site (getSite()) when no context is provided. This allows the existing context-aware converter for RichTextValue to work in all scenarios (nested, schema defaults, etc.) while keeping the output format consistent with standard fields.