practicalli / practicalli/clojure
REPL workflow
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
http://blogish.nomistech.com/repl-based-development/
https://clojureverse.org/t/share-the-nitty-gritty-details-of-your-clojure-workflow/1208
Reloading
https://cognitect.com/blog/2013/06/04/clojure-workflow-reloaded
Debugging
https://cognitect.com/blog/2017/6/5/repl-debugging-no-stacktrace-required
https://clojure.org/guides/repl/enhancing_your_repl_workflow#debugging-tools-and-techniques
Protocols
https://vlaaad.github.io/reveal-repls-and-networking
https://juxt.pro/blog/nrepl
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
Review the linked REPL workflow, reloading, debugging, protocols, and nREPL resources first. The issue does not name a documentation file or define the expected guide structure, so clarify the target location and completion criteria before starting; done should be a project-integrated REPL workflow guide covering the requested topics.
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