markus-moser
commented
2 months ago API requirements
We will need multiple different endpoints to handle the properties tab:
Property Listing
This could be done either as part of the asset detail endpoint or as separate endpoint.
In the classic UI bundle it's part of the asset/document/object detail call:
https://demo.pimcore.com/admin/asset/get-data-by-id?_dc=1712842909851&id=318&type=image
Implementation details
- Important is the destinction of inherited and not inherited properties.
- I don't think that we will need the attributes dao, ctype, cpath and cid as part of the result items - so it's fine when we only have the other ones.
- The config property is related to the configuration in the predefined asset metadata. In case of select properties this shows the comma separated list of properties.
- We need the same approach for assets, data objects and documents. Depending on the solution (detail call vs. separate endpoint) we can decide to do the document part later.
Predefined properties listing
Classic UI call:
Used as source for the predefined properties select box:
Implementation details:
- No paging needed - just add all the items into one call.
Save changed properties for a element
This should be part of the regular asset/object/document update patch call. The full updated list ist sent there. Therefore there are no separate endpoints for updating or deleting a single property of an element needed.
mattamon
https://www.figma.com/file/kTxowT29eCHwNh5NspDGGu/Pimcore-Components?type=design&node-id=490-59345&mode=design&t=l4k909oyeYybtcsS-4 https://www.figma.com/file/kTxowT29eCHwNh5NspDGGu/Pimcore-Components?type=design&node-id=2123-117952&mode=design&t=l4k909oyeYybtcsS-4