Clojurians Log v2
component
I've been thinking about how to make Component a bit more declarative while retaining its good features (simplicity, reliance on protocols & records means better integration with JVM libraries) and I came up with Oreo: • integrates with Aero's facilities to unify application configuration, system definition and component config • makes everything declarative, and thanks to Aero's features allows for interesting system building tricks • very not-even-alpha, I'm using it in a couple of smaller backend services and I still have a few things to finalize (naming, 'API' and REPL workflow) Curious what y'all think :-) https://github.com/lukaszkorecki/oreo
This is interesting. I've started thinking of my systems as having three phases: create, configure, start, and that's what I've been doing with https://github.com/thoughtfull-clojure/amalgam?tab=readme-ov-file#configure-and-run-systems
not exactly the same, but I think in the same vein of thinking about a config that mirrors the structure of your system
(which is kind of like integrant)
That’s the thing - the config in Oreo is the system, it doesn’t mirror anything. I really need to compare Integrant again it’s been a while since last time I tried it
yeah that is more like integrant
This feels like Integrant (which I don't like) so I'll have to sit with this for a bit to decide whether I'd use it or not 🙂
That said, in several of our apps, we build the system map conditionally... although I guess we could still use Oreo for the unchanging core of the system, and then just conditionally add in our dynamic pieces, between oreo/create-system and component/start?
heh, I felt the same when I started working on 3 years ago - I think I added a note about Integrant in the readme
as for conditionally building the system, this works: https://github.com/lukaszkorecki/oreo/blob/main/test/oreo/profile-test.edn
It's seems a bit odd/confusing on first glance that there are three different ways to specify :create fns? #oc/ref! symbol, #oc/ref :keyword, and plain :keyword
that must be a bug in the readme - only #oc/ref and #oc/ref! work now
originally it started just with qualified keywords and symbols, but it was too magical and I still needed to support ref/ref! to configure components
Don't be put off by my initial reactions. I like and use Aero so that's a big plus. I like and use Component so that's a big plus. I may experiment with it in a branch at work if I get time this week...
oh, I'm not put off at all - any feedback is appreciated!
your point about having too many options is definitely valid - I had a hunch that supporting qualified symbols is confusing already, so dropping them and requiring keywords only feels right
Would that completely remove the need for #oc/ref! -- I was confused about the :store comment about it deref'ing an atom there...?
Oreo is basically requiring-resolve under the hood, so I run into this when testing the library with an older codebase:
• a http server component required the Ring handler to be a function, it wouldn't accept a var
• the system also had a couple of stateless components - a function (where passing a var works) but also an atom - so to use it as such, I had to unpack the value from the var obtained via requiring-resolve using deref:
user=> (requiring-resolve 'clojure.walk/postwalk)
#'clojure.walk/postwalk
user=> (class *1)
clojure.lang.Var
user=> @(requiring-resolve 'clojure.walk/postwalk)
#object[clojure.walk$postwalk 0x3c1e23ff "clojure.walk$postwalk@3c1e23ff"]
user=> (class *1)
clojure.walk$postwalk
user=>ref vs ref! - but maybe there should be just ref which does what ref! doesPerhaps #oc/ref and #oc/deref then, to be clearer about the behavior?
nice, I like that
...and done https://github.com/lukaszkorecki/oreo/commit/6c3062b5178bf69eb4a9f2fc5600c80a53f773da