Cloud GET /v1/user-service/my/tasks endpoint 'after' parameter not working

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
api

Research direction

Start with the documented GET /v1/user-service/my/tasks endpoint and reproduce requests using the working limit and deviceId parameters alongside after. Compare the returned tasks for after values such as a record count and task ID; done means the accepted form and its behavior are confirmed and documented.

Written by the indexing model from the issue text.

Description

Hi, I've tried calling the documented GET /v1/user-service/my/tasks endpoint, and found that it works as I expect with the 'limit' and 'deviceId' parameters. But not the 'after' parameter. I've tried assuming it might accept a number of records (e.g. 10) or a task Id (e.g. 1234543) but neither has any effect on the tasks returned. Can you confirm in what form you found success with it?

Dominant language
No language data
Stars
682
Forks
96
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Doridian/OpenBambuAPI

All issues in Doridian/OpenBambuAPI

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.