[MGNLREST-66] Comfortable access to content from apps Created: 14/Oct/15  Updated: 02/Jun/17  Resolved: 02/Jun/17

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 2
Labels: to-specify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
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: MTE > 1.0

 Description   

Improve the get methods so that the out-of-the-box rest endpoints can be used in more situations. A typical front-end developer should be able to use the rest endpoints without too much friction to grab data to use via ajax techniques on a web page - for example for a single page app.

A concept should be created.

Some possible improvements:

  • Return data in a format that is more in line with the standards of rest endpoints - and less JCR-like - for example I would expect properties to be returned as key-value pairs - not as sub objects in JSON.
  • Include the abiltity to include a filter, sort and general query in the json request.
  • Ability to specify which properties to return, or maybe which to exclude as well.
  • Ability to specify how to resolve certain properties on the server. For example if a node has properties that link to an asset and some categories - I'd like to get the URL of the asset and the name and link to the categories - rather that their UUID's.


 Comments   
Comment by Tomáš Gregovský [ 14/Oct/15 ]

Will be nice to have JSON in format of contentMap. Thanks

Comment by Lars Fischer [ 19/Nov/15 ]

I totally support what's in this ticket. As you see in the webinar by Tomas (https://www.youtube.com/watch?v=VedvQF9axdg) he has to fix the result of the get request with an additional JavaScript loop to get rid of unwanted JCR stuff.

Also the resolving of linked data properties is essential (don't give the UUID as only ioption) - if I want to retrieve a list of blog posts via REST then I want to have the associated category names for a post and not the UUIDs.

Of course this all can be solved by writing custom interface logic but this is very tedious and makes the standard interfaces rather useless (if you wnat to avoid ugly interface hacks).

Generated at Mon Feb 12 06:56:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.