Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

OperationAPIIssuesPossible Solution

GET

Anchor
getNode
getNode

Get a Node

  • should return all the data trees when xpath is set to root(/)
  • currently returns only the first data tree
  • modify the existing code for Get a Node API so it returns a List of fragment entities
  • this impacts other API's as well which make use of the Get operation
  • a separate API can be developed to return all the data trees, similar to Get all anchors and Get one anchor API in CPS

PUT

  • Replace a node with descendants

  • Replace list content


  • No issues were found in Delete DataNode API
  • Following tests were performed
    • replacing multiple Data Nodes under one container node
    • replacing multiple Data Nodes under multiple container nodes (under root node xpath)


DELETEDelete a datanode
  • No issues were found in Delete DataNode API
  • Following tests were performed:
    • Individual data nodes were deleted and the ones not deleted were retrieved successfully
    • When all data trees are deleted individually, the entire data node gets deleted from the DB eventually, i.e. an empty collection is not left behind when all data trees are deleted individually
    • When deleting using root node xpath, all container nodes are deleted.


PATCH

Anchor
patchAPI
patchAPI
Update node leaves

Update node API should support Patch operation for multiple data nodes.

  • Patch operation should allow user to update multiple leaf nodes for multiple container/list data nodes.
POSTAdd list element to existing list
  • No issues were detected in Add list element API. The following tests were performed
    • Adding a single list item to existing list in DB
    • Adding multiple list items to existing list in DB
  • The list items are successfully added to the existing list


...