practicalli / practicalli/clojure
Why use clojure.spec
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Having descriptions of your data structures. Being able to validate data against such descriptions. Being to able to generate examples of your data for testing.
https://corfield.org/blog/2019/09/13/using-spec/
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
The issue names clojure.spec and links to an external article, but it does not identify a documentation file, entry point, or tests. Clarify the intended documentation change and acceptance criteria before choosing where to work or how to verify completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100