[MGNLREST-513] Attach multiple reference resolvers to one property Created: 12/Oct/22 Updated: 12/Oct/22 |
|
| Status: | Open |
| Project: | Magnolia REST Framework |
| Component/s: | delivery |
| Affects Version/s: | 2.2.15 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Chris Jennings | 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)
|
| Description |
|
As a developer, I would like to configure a delivery endpoint with multiple reference resolvers for the same property. A client would like to use the Imaging module and the DAM Focal module simultaneously and have their front-end client select whether to use a scaled or cropped image. Both modules provide a reference resolver that, as well as image metadata, expands the JSON response to include a collection of URLs. However, trying to configure a delivery endpoint with both resolvers does not result in both collections being returned: only the first resolver to be declared in included. There may be other applications for this where a system uses custom reference resolvers. |