[MGNLREST-167] mgnl:tags should be returned even when includeSystemProperties is false Created: 17/Jan/18 Updated: 10/Feb/20 Resolved: 17/Sep/19 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| Resolution: | Outdated | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Epic Link: | SPA Editor | ||||||||||||||||||||
| Sprint: | SPA Editor 4, SPA Editor 5, SPA Editor 6 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Description |
|
Content tags are a part of the standard part of a content item and should be returned even when includeSystemProperties is false.
Resolution: Developers can use |
| Comments |
| Comment by Christopher Zimmermann [ 09/Sep/19 ] |
|
I see the related Lets discuss! Because I can also see that the above introduces some kind of inconsistancy. What I want to prevent is that every rest endpoint declaration has to include:
|
| Comment by Robert Šiška [ 13/Sep/19 ] |
|
The only way I see that makes sense would be to allow all "mgnl:*" properties by default. Treating only mgnl:tags (only present in ee, btw) differently would make no sense in rest module. |
| Comment by Christopher Zimmermann [ 13/Sep/19 ] |
|
No, wouldn't want to do that. |
| Comment by Christopher Zimmermann [ 17/Sep/19 ] |
|
We agreed via a Slack discussion that this is solved by enabling developers to configure which systemProperties are delivered via the new If this is not satisfactory with customers and partners we can re-evaluate this in the future. |