practicalli / practicalli/clojure
coding practices
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Clojure style guide - https://github.com/bbatsov/clojure-style-guide
Clojure core library specific guidelines - https://dev.clojure.org/display/community/Library+Coding+Standards
Linters - Eastwood
https://github.com/jonase/eastwood
https://atom.io/packages/linter-eastwood
http://www.bradcypert.com/2017/06/28/clojure-kibit-eastwood/
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 reviewing the linked Clojure Style Guide and Clojure core library coding standards, then compare them with the Eastwood and linter-eastwood references. The issue does not identify a documentation file, specific practices to add, or acceptance criteria, so the intended scope and definition of done need clarification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100