practicalli / practicalli/clojure
Idiomatic Clojure - code smells
Open
Nobody has claimed this yet.
idiom
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
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 the linked code-smells article and inspecting the repository's documentation structure; no file, test, or entry point is identified in the issue. Before work can begin, clarify whether the goal is to add or revise documentation and define which code smells and expected content are in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100