Details
-
Story
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
None
Description
As a developer I want to get the relevant referenced content in a predictable and errorfree way.
The reference resolving is a useful and popular feature, but the way it is configured causes problems for developers.
- Name conflicts: Currently you only supply a property name. It can eaasily happen that multiple content items have the same property name, and you might get things resolved not in the way you intended. For example if you have an "image" property - you might want to handle it differently in different components, but this is not possible.
- The REST response returns the entire content item, where you might only want a few properties. (Like in a page.)
Checklists
Acceptance criteria