[MGNLREST-755] Allowing to define mutliple propertyNames for reference Resolver Created: 28/Sep/23 Updated: 23/Oct/23 |
|
| Status: | Open |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | 2.2.22 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christoph Damm | 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: |
| Description |
|
Hello, wouldn't it be nice to be able to define a list of propertyNames for a reference resolver within a delivery endpoint definition? E.g. when having multiple page links on a component/page and all of those shall be resolved with the same resolver.
Cheers,
Chris |
| Comments |
| Comment by Christoph Damm [ 29/Sep/23 ] |
|
Just another info: for now i helped myself with includes for the resolver configuration itself, so that that isn't duplicated all the time, still beeing able to have multiple properties being handled by the same resolver would be nice and cleaner i think. |
| Comment by Christoph Damm [ 09/Oct/23 ] |
|
Update: I submitted the above as a suggestion to the roadmap as i was made aware within another Jira ticket of mine, that this would be the correct way. So feel free to close this one as well, if need be. |