purescript / purescript/pursuit
Remove redundant "purescript-" prefix
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
By now there are no more packages without the "purescript-" prefix on Pursuit. So maybe we should just not show it anymore? It adds a lot of visual noise and the listing would be much nicer without it.
What is actually the future of the "purescript-" prefix? If I remember correctly this was a way to avoid name collisions with JavaScript packages on Bower, but with a switch to purescript/registry this won't be necessary anymore, right?
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
No file, test, or entry point is named. First inspect how Pursuit builds and renders package listings, then trace where the "purescript-" prefix is displayed and review the registry migration context. Done means the intended prefix behavior is decided and the listing consistently reflects it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100