#Which API do you like better?
1 messages · Page 1 of 1 (latest)
Interesting question. I can definitely see the appeal of both. I would personally lean towards the first option I think
Interesting... care to elaborate why?
I can also argue for both, but most of all, I'm looking for consistency across various packaging solutions.
The second one is more like how Dagger publishes containers today.
In general I've approached modules that wrap tools to expose an API that resembles the underlying tool. But that might just be my personal preference 🙂
Hm, yes, that's another interesting topic. That's been my approach as well, but lately I feel the need for "higher level" modules.
Example of that:
arc: "low level" module wrapping an archiver tool called arc: https://github.com/sagikazarmark/daggerverse/tree/main/arc
archivist: "high level" module built for reuse (eg. implements a simple interface): https://github.com/sagikazarmark/daggerverse/tree/main/archivist