[MGNLREST-28] Nodes and properties should be handled by separate endpoints Created: 05/Nov/13  Updated: 12/Nov/13  Resolved: 06/Nov/13

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

Type: Improvement Priority: Neutral
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
Resolution: Fixed 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)
Date of First Response:
Epic Link: REST support
Sprint: 5.2-rc1

 Description   

/nodes/v1/

{workspace}/{path}

GET
- can get full tree
- returns 404 if path does not exist

POST
- returns 404 if path does not exist
- can not post full tree
- does not return the node to save bandwidth

PUT
- can not put full tree
- does not return the node to save bandwidth

DELETE
- returns empty response
- returns 404 if path does not exist


/properties/v1/{workspace}

/

{path}

basically shortcuts for the node operations with tiny posts

GET

  • returns only the value
  • returns 404 if path does not exist

POST

  • returns 404 if path does not exist
  • returns empty response

PUT

  • returns empty response

DELETE

  • returns 404 if path does not exist
  • returns empty response

includeMeta argument should be includeMetadata



 Comments   
Comment by Daniel Lipp [ 08/Nov/13 ]

Make sure to also adapt the web-access permissions in userroles.rest.xml - no /.rest/repositories but /.rest/nodes + /.rest/properties...

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