[MGNLREST-273] Allow requests for a restricted set of fields (sparse fieldsets) Created: 02/Sep/20 Updated: 02/Sep/20 Resolved: 02/Sep/20 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| 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: | |||||||||||||||||
| Description |
|
Citing: https://jsonapi.org/format/#fetching-sparse-fieldsets
Examples: https://jsonapi.org/examples/ |
| Comments |
| Comment by Mikaël Geljić [ 02/Sep/20 ] |
|
Magnolia does *not* specifically adhere to this JSON:API spec—which is not backed by any significant standard nor community process. Name of that alleged spec is also debatable as it may bring lots of confusion. We should also not refer to it in REST module documentation, if that's the case. Meanwhile, the story here is a duplicate of |