purescript / purescript/pursuit
Go to the equivalent page when switching versions, if possible
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
If I am on the page for the Data.Maybe module version 0.3.2, and I use the version selector to select 0.3.1, then I should be taken to the Data.Maybe module for 0.3.1, not the package homepage for 0.3.1.
If that module does not exist, then I think it's ok to show a 404 page, as long as it explains what happened.
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
Begin by tracing the version selector flow for a module page and how it handles a selected package version. Check how the equivalent module URL is resolved and how missing modules are rendered. Done means switching versions preserves the module when it exists, while a missing module produces an explanatory 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100