CLI spec for alternate backends
Open
Nobody has claimed this yet.
alternate backends
- Dominant language
- PureScript
- Stars
- 831
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
In #426 we added basic support for alternate backends.
As discussed in https://github.com/spacchetti/spago/issues/355 we should write down a "CLI spec" that alternate backends can conform to so that they'd work with Spago out of the box.
Contributor guide
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 reading issues #426 and #355 to understand the existing alternate-backend support and the expected CLI behavior. Define the CLI contract alternate backends must follow so they work with Spago out of the box, and document that specification. Done means the requirements are written clearly enough for backend implementers to conform to them.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100