Metaculus / Metaculus/metaculus
MC timeline doesn't respect if CP terminates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 34
- Avg merge
- 16h 34m
- Merged PRs (30d)
- 30
Description
MC timelines don't indicate when the CP terminates because all existing predictions expire. It's a very rare situation & mostly inconsequential, but technically incorrect.
Similarly, withdrawal on MC timelines isn't indicated for user predictions.
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 locating the MC timeline rendering and the logic that handles expired predictions, then trace how CP termination and user-prediction withdrawal are represented. Confirm the timeline visibly indicates both cases instead of showing only expired predictions, and add or update the relevant tests if they exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100