This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-27
Channels
- # announcements (7)
- # aws (1)
- # beginners (42)
- # calva (65)
- # clj-kondo (5)
- # cljs-dev (11)
- # clojure (69)
- # clojure-australia (7)
- # clojure-dev (4)
- # clojure-europe (9)
- # clojure-gamedev (2)
- # clojurescript (2)
- # conjure (4)
- # cursive (1)
- # data-science (1)
- # datomic (8)
- # events (1)
- # fulcro (35)
- # graalvm-mobile (40)
- # introduce-yourself (1)
- # lsp (26)
- # malli (14)
- # mathematics (2)
- # missionary (5)
- # nextjournal (4)
- # off-topic (4)
- # polylith (10)
- # shadow-cljs (5)
- # test-doc-blocks (1)
- # tools-build (24)
- # tools-deps (1)
- # xtdb (12)
https://github.com/lread/test-doc-blocks v1.0.166-alpha - Test AsciiDoc and CommonMark code blocks found in articles and docstrings
• Added traditional main invocation as an alternative to -X
invocation for more a more general purpose entry point
• See https://github.com/lread/test-doc-blocks/blob/main/CHANGELOG.adoc#v10166-alpha for details and other changes
• Drop by in #test-doc-blocks should you want to chat!
ooooh very cool!
this might deserve to be in the alternatives section? https://github.com/hyperfiddle/rcf
Yeah, certainly related @U02N27RK69K, thanks!
There's been a few updates to https://github.com/juxt/clip, we're now on 0.26.0. This release marks the end of my worries that Clip will have any major breaking changes, I believe it is now very close to outgrowing its alpha status.
Clip is a dependency injection library similar to Integrant and Component. Its aim is to "clip on" to your existing program without requiring multi-methods or protocols. The rationale in the README explains this in a lot of detail.
Changes in the last few releases:
• BREAKING: symbols are no longer resolved to functions for :executor
and :deref
, you now need to call juxt.clip.edn/load
manually
• AOT
◦ There's a new require
function which will require the namespaces for a system to start or stop
◦ I'm aiming for Clip to work inside GraalVM, but I haven't yet given this a go. Please let me know.
• Testing
◦ You can now start a subset of a system, so you can start a handler and its dependencies
◦ You can select
a subset of a system, and perform any operation on that (like select-keys
for a system)
◦ There's a new macro with-system
which will run a code block with a system started and attempt to clean it up afterwards
• :resolve
is now only called once, rather than on every reference
• Documentation got a makeover
In the future, I'd like to look at opening up the operations on a system to user customization. I'm no longer interested in suspend/resume, but I'd like to allow that to be implemented in user space. I'd also like to continue the work I did on "indirect linking," which allows you to re-eval a ring handler and not need to restart your system.