authgear / authgear/authgear-server
Change cursor to real cursor to avoid performance issue in Admin API
Open
cooldown/minor-feature
- Dominant language
- Go
- Stars
- 2k
- Forks
- 125
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 32
Description
When fixing the issue https://github.com/authgear/authgear-server/issues/3176
It's been brought up that the cursor we are using in the admin API is an offset. This may cause performance issue.
Contributor guide
Research direction
Start by reading issue #3176 and locating the Admin API pagination implementation that currently represents a cursor as an offset. Trace how the cursor is generated and consumed, then verify that the completed change uses a real cursor and avoids the stated performance issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100