@weavejester Is there an ETA for the next version release? I could use the RefLike
protocol / public normalize-key
function. No rush, just wondering
What do people do about errors in integrant init methods? There doesn't seem to be any built in rollback for already started components, and exceptions mean I don't get hold of even the partially created system to let me manually stop them.
The RefLike
protocol is going to be pushed into a branch rather than releashed, as there’s more work to be done on it than we first thought.
The normalize-key
function will be released in an 1.0 alpha at some point, but as it’s only a one-line function you could always just add it yourself if you need it right away.
Yeah the normalize-key isn't a big problem, the reflike a bit more. Is there a public discussion about what needs to be done for RefLike?
The exception contains the partially started system, so you can use that for rollback.
ohhhh, apologies, did not spot that
Thanks
Basically we need to expand the protocol to account for mandatory/optional dependencies. But there may also be other issues hiding away, so I’d like to push RefLike
back for now. I’d rather focus on getting Integrant 1.0 released, and currently my work is on Ring, so even that will take me a few months to get around to.
I'm not quite sure what the problem is, quickly reading this thread. But I'll check it out later again. Are there specific features you want to develop before version 1.0 ?
We're using Duct / Integrant and going to be using it a lot more at the company where I work. So if I can, I'd gladly lend a hand
I want to make at least one small breaking change before 1.0 (see the issue I linked before), but apart from that it’s feature complete for 1.0. The RefLike update will likely be a 1.1 thing.
Also Integrant-REPL has automatic rollback for REPL/development work.