pomegranate
test-runner
pomegranate | test-runner | |
---|---|---|
6 | 3 | |
497 | 276 | |
0.6% | 1.1% | |
5.5 | 0.0 | |
10 days ago | 2 months ago | |
Clojure | Clojure | |
- | Eclipse Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pomegranate
-
Spinneret: A modern Common Lisp HTML generator
https://github.com/clj-commons/pomegranate
-
strawpoll: lein vs deps preference by Clojure vs CLJS
However, to do this it uses the same library lein uses for dependency resolution and classpath creation. And of course you can integrate with either deps.edn or project.clj.
-
What is the best way to load a lib while in repl?
You are looking for pomegranate
-
How can I test my clojure code without re-jacking in every time?
You can try https://github.com/clj-commons/pomegranate
-
REPL-Driven Development - Clojure's Superpower by Sean Corfield - @ LndClj
He mentioned that he's using the add-lib3 branch of tools.deps.alpha to get hot-loading dependencies. If you use lein instead, the pomegranate library enables it.
-
Why Clojure?
The only time I need to restart is when I load new libraries but you can use https://github.com/clj-commons/pomegranate
test-runner
-
Clojure is a product design tool
> I had to Grok Integrant again because I wouldn't understand my project otherwise.
You can use plain functions and `reduce` for system composition if you want. Take a look at how Biff does it: https://biffweb.com/p/thinking-about-system-composition/
DI should be used sparingly for the top-level, stateful pieces of your system. If you can't understand your program without it, is this a problem with Clojure itself or the design of the program?
> And when it comes to best practices around unit testing, it's another one of those things where no one in the community seems to be sharing much about it.
The `clojure.test` API has stayed the same for the last decade and that's what you'll see in most projects. Is the concern about how to run tests? Both of the following libraries work well:
Minimal test runner: https://github.com/cognitect-labs/test-runner
-
Build and run Clojure projects. CLI, tools.deps and deps.edn guide
:aliases {:test {:extra-paths ["test"] :extra-deps {io.github.cognitect-labs/test-runner {:git/url "https://github.com/cognitect-labs/test-runner.git" :git/sha "8c3f22363d63715de4087b038d79ae0de36a3263"}} :main-opts ["-m" "cognitect.test-runner"] :exec-fn cognitect.test-runner.api/test}}
-
How can I test my clojure code without re-jacking in every time?
Cognitect's test-runner is probably the most commonly used approach with deps.edn and the CLI: https://github.com/cognitect-labs/test-runner
What are some alternatives?
parinfer-rust - A Rust port of parinfer.
kaocha - Full featured next gen Clojure test runner
rlwrap - A readline wrapper
vscode-calva-setup - My VS Code / Calva / Portal / Joyride setup
timbre - Pure Clojure/Script logging library
xforms - Extra transducers and reducing fns for Clojure(script)
rain - 🌧️ A Clojure/Script library for fast and flexible web apps.
lispy - Short and sweet LISP editing
clj-new - Generate new projects based on clj, Boot, or Leiningen Templates!
figwheel-main - Figwheel Main provides tooling for developing ClojureScript applications
imba - 🐤 The friendly full-stack language