Changed endpoint format for GET,PUT, DELETE for multiple objects of Class and Collections #590
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #587
Checklist
Current behaviour
The current API's endpoint format for operations on collections and deletion/insertion of multiple objects is :
Which isn't conventional and there is repetition of keywords like
add
anddelete
.Also, we had lot of code repetition in resource.py ( Items, ItemMember, ItemMembers to operate on single and multiple objects ) when most of it can be done using Item and ItemCollection resource classes with some additional params in request endpoint.
New expected behaviour
Previously, if a user wanted to create multiple objects of a Class, he/she had to pass ids in endpoints as well which can be really time consuming if one wants to PUT multiple objects by making request to a Class endpoint.
PUT (without ids):
Request Body:
PUT ( with ids ):
Response :
DELETE ( multiple Class objects):
Response :
DELETE ( Multiple members from a Collection)
Response:
Change logs