Allow for tasks with a query type of fixed size and no maximum batch size
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
DAP draft-09 changes the fixed size query type such that the maximum batch size is now optional. Currently, divviup-api uses the nullability of max_batch_size to signal what the query type is. We will need to disentangle this to fully support draft-09.
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing how divviup-api represents query types and uses max_batch_size to distinguish them. Compare that flow with the DAP draft-09 fixed-size query definition, then identify the affected validation and serialization paths. Done means fixed-size tasks work when maximum batch size is absent without relying on nullability to determine the query type.
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
- 35/100