purescript / purescript/pursuit
API
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
As I've been thinking about package management, I keep thinking that modifying Pursuit to be more API-based would be a good thing, allowing fine-grained queries on the database which could be used by a package manager written in PureScript.
This might be a good thing to bundle with a move over to Postgres if we decide that's a good idea.
Maybe this could form part of a GSOC project, as part of a larger package manager project.
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 files, tests, or entry points are named. Start by reviewing Pursuit's current API and database boundaries, then determine whether a Postgres migration is in scope. Done means a concrete, agreed scope for fine-grained queries and package-manager use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, postgres
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100