[MGNLREST-136] Always return @nodeType and @id properties Created: 26/Oct/17 Updated: 12/Mar/18 Resolved: 28/Nov/17 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Dai Ha |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 1h | ||
| Time Spent: | 2.5d | ||
| Original Estimate: | 1.5d | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | REST Queries |
| Sprint: | Saigon 121, Saigon 122, Saigon 123, Saigon 124 |
| Story Points: | 2 |
| Description |
|
Return @nodeType and @id property always, even when includeSystemProperties is false. |
| Comments |
| Comment by Christopher Zimmermann [ 13/Nov/17 ] |
|
I realize that Magnolia ContentMaps (used in tempalting) expose '@uuid' and '@id'. I wonder which of these would be better to return in rest. I like '@id' since it is more generic and could be used for contentTypes which could be backed by content sources that dont have uuids, but do have ids. |
| Comment by Christopher Zimmermann [ 13/Nov/17 ] |
|
After discussion with services, I think we should indeed use @id instead of @uuid. Open for discussion if there is disagreement, but I will change the description and summary to reflect the change. |
| Comment by Dai Ha [ 14/Nov/17 ] |
|
I have no problem with using @id instead of @uuid, to me its the same mean and neat. |