parseDuration("1h30m") returns 3600000 — the 30m is silently dropped

Open Beginner friendly
#7 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
tooling

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.

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
Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sorrycc/test

All issues in sorrycc/test

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.