Tiberiu Ichim

The question is: Should plone.restapi expose any stuff that's specific to a particular frontend? The view names are specific to Plone Classic. Perhaps it's not Volto that needs the integration...

missing = "I'm empty but here's my value". I can understand the case where you're creating an object, it comes with a default value, but then the user decides that...

@wesleybl @rpatterson Although I'm not on the EEA team which is currently handling this feature request, I think I can add some insight. We currently have a Volto website (eea.europa.eu/ims)...

Side info, but maybe good to know: we use 'paqo' in the serialized p.a.querystring query for the URL, in search block: https://github.com/plone/volto/blob/master/src/components/manage/Blocks/Search/hocs/withSearch.jsx#L177

It seems like `@source` bails out early if there's no field found. https://github.com/plone/plone.restapi/blob/34dc327285efe85ac7ee2bac73905f7352818bc8/src/plone/restapi/services/sources/get.py#L35 I think it should take into consideration the CatalogSource use case, which is a context-less source.

Solved by pending PR https://github.com/plone/plone.restapi/pull/917

+1 looks good, seems semantic.

@jenkins-plone-org please run jobs

@jenkins-plone-org please run jobs

@jenkins-plone-org please run jobs