Clojurians Log v2

What is a proper way to provide a different implementation of a boundary in dev versus prod?

Cannot find an example

So I want a component to depend on an abstraction

You give the prod and dev implementations different keywords, deriving from the same base.

And then provide in config what implementation of the abstraction I use

Is there an example somewhere?

Thanks 🙂

I can’t think of one off the top of my head. Let me sketch one out for you.

Great I basically have a defprotocol with two implementations

Two deftypes

Okay, so you’d write init-key methods for both of them:

(defmethod ig/init-key ::dev [_ opts]
  (->DevType opts))

(defmethod ig/init-key ::prod [_ opts]
  (->ProdType opts))

And then in your duct_hierarchy.edn you’d put something like:

{:app.foo/dev [:app/foo]
 :app.foo/prod [:app/foo]}

So they derive from the same parent.

Then you put the dev one in your dev profile, and the prod one in your prod profile.

And refer to it using the parent keyword, e.g. #ig/ref :app/foo.

That way the reference will choose whichever key (dev or prod) is in your configuration.

Thanks took some time to digest and implement, but works like a charm now