oxidecomputer / oxidecomputer/omicron
Sort paginated results by `time_created`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The proximate need comes from update deployments. Time order is pretty central to the concept of update history. In the console we want to display them by most recent first. But this is a pretty general concept that would be useful across many endpoints. You can easily imagine wanting to sort instances by created, or modified, or the last time runtime state was updated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or specific endpoint. Start by locating the paginated API result and pagination-handling entry points, then trace how ordering is currently defined. Done means the API supports the requested time-based ordering consistently for the relevant paginated results, with coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100