This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-07
Channels
- # announcements (13)
- # atom-editor (3)
- # babashka (53)
- # beginners (28)
- # clojure (30)
- # clojure-australia (4)
- # clojure-europe (22)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-norway (14)
- # clojure-spec (8)
- # clojure-uk (8)
- # clojurescript (19)
- # cursive (33)
- # datomic (4)
- # defnpodcast (6)
- # events (3)
- # fulcro (3)
- # graalvm (77)
- # jobs (2)
- # juxt (11)
- # podcasts-discuss (1)
- # reitit (1)
- # releases (2)
- # remote-jobs (2)
- # sci (1)
- # shadow-cljs (27)
- # sql (6)
- # testing (10)
- # tools-deps (36)
- # vim (4)
- # xtdb (15)
It is not always easy writing a CLJC library, having to handle both Clojure and Clojurescript. So here is a little template that might help you: https://github.com/helins/templ-lib.cljc Not saying that it is perfect (it isn't), but you might get some inspiration 🙂
Happy to take PRs though, if there are obvious improvements that can benefit everyone
Great! I am one that looks for templates when I am about to do something new. Last time I made a cljc library, I noticed the lack for templates here. 😀
having authored similarly focused templates, one thing I'd recommend is to template the CI integration as well. Especially featuring a comprehensive test matrix
@U45T93RA6 Quite right! Although I am not sure if it should be part of the template itself. I often disliked templates where you have to spend some time removing everything you don't want. So for the time being at least I've added it to an "extra" folder in the repo.
test.check
is a wonderful tool. It helps me find edge cases even in very simple, dumb assertions. For any non-trivial example, it is a bliss.
However, from experience, it is often hard locating precisely what make a test fails in any non-trivial example. I hope this couple of lightweight abstractions will help you as much as they helped me in organizing your generative tests and being highly productive: https://github.com/helins/mprop.cljc
This looks interesting. Would it make sense to add an example or two about how failing test output compares to when multiplexing isn't used?
A typo in the Readme :effictive
@U08BJGV6E Indeed, it was maybe too abstract. I added outputs in README, hopefully it's clearer
During the weekend I've made a really simple text-to-speech application which demonstrates the power of holy-lambda, AWS Polly, babashka runtime and scittle. Hope you will like it guys. Demo: https://youtube.com/watch?v=XJc6xma7v0Ahttps://t.co/uQ0JlE0N0p?amp=1 Project: https://github.com/FieryCod/holy-lambda/tree/master/examples/bb/babashka/talk-with-babashkahttps://t.co/vsFHiGVkU8?amp=1
I'm happy to announce a new release of Mirabelle (https://github.com/mcorbin/mirabelle), a stream processing engine for monitoring heavily inspired by Riemann (http://riemann.io). I also wrote recently a documentation website for it (https://www.mirabelle.mcorbin.fr/), and published today an article about how I use it for blackbox monitoring (https://www.mcorbin.fr/posts/2021-06-07-mirabelle-cabourotte-blackbox/). As always, i'm open for feedbacks 😉
Mirabelle use the same protocol than Riemann. - should be "as"? Streams clocks -> Streams' clocks?