Mikel Larreategi
Mikel Larreategi
@ionlizarazu
~~After this PR, we will be always requesting to expand the `@navroot` component of the REST API. We are already doing that for the `@translations` endpoint in a multilingual site,...
~I have reworked this to use explicit dispatch calls to `@navroot` and `@site` instead of relying on expansion~
And what about delegating this configuration to plone.volto? We can add a preconfigured search page with a search block when installing plone.volto.
For complete reference in classic Plone we are using `i18n:translate` and `i18n:name` tags to handle those translations: https://github.com/plone/plone.app.event/blob/master/plone/app/event/browser/formatted_date.pt#L13
How does Plone Classic UI behave in such case?
I think that this suggestion does not work. I think that we need something with parameters like in Classic UI: https://github.com/collective/plone.app.locales/blob/master/plone/app/locales/locales/plone.pot#L8866-L8883
Last week I tried unsuccessfully to build such messages trying to keep existing HTML, but it should be possible like @tiberiuichim suggests
Serializers are adapters and are defined here: https://github.com/plone/plone.restapi/tree/master/src/plone/restapi/serializer If you need to serialize some other attributes, you need to write your own adapter and register it for your Interface of...
OK then, per brain customization can't be achieved through this kind of adapters.