Clojurians Log v2

Thanks for the positive feedback. Though it looks like I'll need to explain the 'seam' a little better in the documentation! The :system key contains an Integrant configuration. It's as straightforward as that. Modules expand out into additional keys using the expand-key multimethod, but any configuration you add overrides that expansion. So to give an example, suppose you have a :system configuration like:

{:duct.module/sql {}}

{:duct.database.sql/hikaricp
 {:jdbcUrl #ig/var jdbc-url, :logger #ig/refset :duct/logger}
 :duct.migrator/ragtime
 {:database #ig/ref :duct.database/sql,
  :logger #ig/refset :duct/logger,
  :migrations nil,
  :strategy :rebase}
 :duct.repl/refers
 {db duct.repl.sql/db, sql duct.repl.sql/sql}}

{:duct.module/sql {}
 :duct.database.sql/hikaricp
 {:connection-timeout 10000
  :maximum-pool-size 32}}

Thank you for the quick reply, James. This makes perfect sense and is as simple and straightforward as I hoped it would be. 🙂

Hi, don't worry about pinging me - answering questions like this is what this channel is for. First, it's worth mentioning that the Duct Reitit router has inbuilt support for coercing and validating via Malli schema. Is that sufficient, or do you need more complex validation? When you say you've added the middleware map, how exactly are you doing it? Perhaps there's something that you've missed or gotten slightly wrong, so being able to see your configuration (or at least the relevant parts of it) would really help.

James, thank you for your reply. I will make another attempt to understand Reitit and its interaction with Malli schemas for coercion and validation next. I apologize for the open-ended nature of my question. Reading your reply, I think the root cause of my issue is not Duct, per se, but a lack of helpful, complete, easily accessible documentation about how to leverage Reitit and Malli. And I assure you, my inability to find it is not from any lack of trying. 😞

That's probably somewhere we can improve the docs then. In a nutshell though, you can add Malli schema to parameters via the :parameters key on a route to validate and coerce data from the request map. So in general the format goes:

{:duct.module/web
 {:routes
  [[ROUTE {:parameters {PARAM-LOCATION MALLI-SCHEMA}}
   ...]]}}

{:duct.module/web
 {:routes
  [["/example/:id"
    {:parameters
     {:path {:id [:int {:min 0}]}}}]]}}

{:duct.modules/web
 {:routes
  [["example/:id"
    {:parameters
     {:path [:map [:id [:int {:min 0}]]]}}]]}}

Thanks for the clarification and the example. I am reading through the Reitit Malli coercion page again -- https://cljdoc.org/d/metosin/reitit/0.9.2/doc/coercion/malli -- and the Malli GitHub README, and they align with what you've written above. Thanks!

I think it's probably worth me adding a section on coercion/validation to the docs, as the otherwise the documentation is spread across Malli, Reitit and (to a small extent) Duct itself.

And I see now that the ever-helpful Kari Marttila published a useful blog post on this also -- https://www.karimarttila.fi/clojure/2020/12/07/malli-clojure-library.html Thanks again!

BTW, James, I just did some testing to see if I could induce data validation errors by violating the Malli schema, and it worked as expected. 🙂