Contend with time precision changes in Janus 0.9
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
The Janus 0.9 series will change how times are represented so that absolute times and durations are now multiples of a task's time precision. This has implications for divviup-api:
- will need to deal with both Janus 0.7 and 0.9 and up, based on an aggregator feature flag
- we need to decide how to represent this in divviup-api's API and the console
- some basic UX for this? Perhaps if we detect the
TimePrecisionfeature, we put big red warnings on the task creation form saying "HEY DID YOU DOUBLE CHECK YOUR TIME MATH?"
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 the divviup-api API and console paths involved in task creation, then inspect how the aggregator feature flag and Janus TimePrecision capability are exposed. Define how Janus 0.7 versus 0.9 time precision should be represented in the API and console; done includes an agreed UX for warning users about time math.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100