-
Notifications
You must be signed in to change notification settings - Fork 187
Closed
Milestone
Description
Proposal:
Why do you avoid to return links attribute of the task api response ? Can you restore the possibility to use next link? Or introduce a
def find_tasks_paged(self, **kwargs):
"""List all tasks.
:key str name: only returns tasks with the specified name
:key str after: returns tasks after specified ID
:key str user: filter tasks to a specific user ID
:key str org: filter tasks to a specific organization name
:key str org_id: filter tasks to a specific organization ID
:key int limit: the number of tasks to return
:return: Tasks
"""
return self._service.get_tasks(**kwargs)
with also links sectin in response?
Current behavior:
No link with next task id will be returned because only tasks will be returned
def find_tasks(self, **kwargs):
"""List all tasks.
:key str name: only returns tasks with the specified name
:key str after: returns tasks after specified ID
:key str user: filter tasks to a specific user ID
:key str org: filter tasks to a specific organization name
:key str org_id: filter tasks to a specific organization ID
:key int limit: the number of tasks to return
:return: Tasks
"""
return self._service.get_tasks(**kwargs).tasks
Desired behavior:
Have the next link into the response to implement pagination and retrieve all tasks (if more than 500) or use smaller chunk during the inquiry
Use case:
Because no pagination method be possible
francescobianca