parseDuration("1h30m") returns 3600000 — the 30m is silently dropped
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Single units work fine ("2h", "30m", "45s"), but combined durations lose everything after the first segment:
import { parseDuration } from "./src/parseDuration";
console.log(parseDuration("1h30m"));
// got: 3600000 (= 1h)
// expected: 5400000 (= 1h30m)
console.log(parseDuration("2m30s"));
// got: 120000 (= 2m)
// expected: 150000
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 at src/parseDuration and reproduce the two combined-duration examples from the issue. Verify that parsing "1h30m" returns 5400000 and "2m30s" returns 150000, while the existing single-unit behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100