Fork me on GitHub

The release 0.4.0 of PGMig is out What's new: • Native image capability to connect via TLS. • More command line options checks. Breaking changes • Command line options have the highest priority (overriding environment variables) • Environment variables have been changed to match psql environment • Updated to GraalVM 20.2.0. • No verbose logging defaults. Gihub: Pre-built x86_64 linux docker image is available at dockerhub (

🎉 12

I've released [org.clojars.rutledgepaulv/ring-firewall-middleware "0.1.3"]. This release adds middleware for limiting or throttling concurrency and middleware for limiting or throttling request rates. The limits and throttles can be imposed globally or per some function of the request (useful for implementing per user or per tenant limits).

🎉 15

Nice Paul! Killin' it per usual :-)

👋 6

After a year in incubation, we are proud to present Malli, a new data validation and specification library for Clojure/Script! Big thanks to Clojurists Together for helping to ship it out. Introduction post: In short, Malli covers: • schema definitions, as data • support for open and closed maps • data validation and error reporting • humanised and localised error messages • spell-checking of map and multi keys • bi-directional value transformation • value and schema generation • tools for programming with schemas • support for JSON Schema, Swagger and DOT • open apis for both end users and extenders Coordinates: • Github: • Clojars: • Slack: #malli On behalf of Metosin and all contributors, Tommi

🎉 204
🍾 72
parrot 63
sheepy 24
👏 42

awesome! already have a really good use case at work. Thanks!


Great project. I'd suggest striking this from your blog post: > Spec builds around [...] strong ideologies [...] Malli [...] aims to be pragmatic. The world is not perfect, it's ridden with nulls and optional keys and we should embrace them. The link on "ideologies" to "Maybe Not", followed by the contrasting distinction of pragmatism appears to misconstrue the talk: optionality fused to the container spec is a trap, and it is more practical to compose optionality specs for specific contexts.

☝️ 3

I think this is an interesting point by @U09QBCNBY, @U055NJ5CC


This is really great, congrats! I am using the library currently mainly for input validation for our project at work, and it performs flawlessly (being aware that I am severely under-utilizing it currently)


@U09QBCNBY i think that comparison to spec is more valid for spec 1, the changes hinted at for spec 2 would make it a weaker argument


thanks for the feedback. I could have used better wording (maybe strong opinions about optionality?) and done better job explaining: Spec2 removes support for explicit optionality, making optionality an implicit subtraction of schema and select. For designing new things with Clojure, this might be a good thing, but when interacting with the outside world with optionality and closeness baked in, these opinions make things harder.