[MGNLREST-682] ReferenceResolvers has namespace clashes and content is hard to control Created: 25/Apr/23  Updated: 23/Oct/23

Status: Open
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Headless Backlog
Team: DeveloperX

 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.)

Generated at Mon Feb 12 07:02:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.