Open Manvityagi opened 3 years ago
@Manvityagi I would like to work on this Plz assign
@Manvityagi Is this issue still open? If yes then I would like to work on this!
Issues are assigned on FCFS basis, so I'm assigning this issue to @ritik307 @Vishal1003 please find some other issue to work upon.
@Vishal1003 It has been assigned to you. I think @ritik307 is not available as of now.
@Manvityagi if this issue becomes available in future, I would like to work on it.
@Vishal1003 Please respond if you're working on this issue, otherwise I'll have to unassign you from this issue.
@vaishali614 I'm really sorry. I won't be able to work on this issue as of now.
@Manvityagi if this issue becomes available in future, I would like to work on it.
Awesome @akshitakanojia. I have assigned to you, Feel free to comment here if you face any difficulties in implementation.
@Manvityagi is it possible to get total number of pages as well in the api response, as it will be required to show the page numbers. Otherwise I can show only prev current next.
@Manvityagi is it possible to get total number of pages as well in the api response, as it will be required to show the page numbers. Otherwise I can show only prev current next.
Hey, yeah. We can do that. Would you mind creating that issue in backend?
okay I'll create.
[x] I checked to make sure that this issue has not already been filed.
[x] I'm reporting the issue to the correct repository (for multi-repository projects) (optional)
Expected Behavior:
Users should be able to move from one page to another
Current Behavior:
All the results are shown. There is no pagination.
Solution:
The GET API can take 2 query params -
page
andlimit
. Make use of them while calling APIs and retrieving results. Default value is page=1 and limit = 10.API Documentation