You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, API endpoints, which handles list of objects (such as VPs) does not display properly if there are more pages in the response. One of the such endpoint is Trustchain API.
Requirements
We need all the API endpoints, which handle list of objects in their responses, needs to display in much properly manner like the response could have a field "next_url" field to help loop through the results or field such as "total_pages" and "total_results"
Definition of done
Improving all the API endpoints involving pagination and make sure their responses are properly displayed.
Updating documentation.
Acceptance criteria
100% completion as mentioned in DOD.
The text was updated successfully, but these errors were encountered:
It's not clear where the issue has been observed, if this can be clarified it'd be great please. We suspect that the report here records the situation when the headers might have been (wrongly) expected for responses from inside the Policy. These would feature in such responses only when the Document block contains paginationBlock. When this is the case the response to the get request to the paginationBlock would contain total count.
Problem description
Currently, API endpoints, which handles list of objects (such as VPs) does not display properly if there are more pages in the response. One of the such endpoint is Trustchain API.
Requirements
We need all the API endpoints, which handle list of objects in their responses, needs to display in much properly manner like the response could have a field "next_url" field to help loop through the results or field such as "total_pages" and "total_results"
Definition of done
Acceptance criteria
100% completion as mentioned in DOD.
The text was updated successfully, but these errors were encountered: