#Extensions

1 messages · Page 1 of 1 (latest)

formal crow
#

So... I was chatting with @spare orchid about some of this stuff yesterday... and @torn wing this morning.

And it had me realize that we really need a way to allow a user to define the extensions the need without an external file. No dagger.mod or similar.

Because we need to allow users to create static binary CLIs for their pipelines. And they shouldn't have to carry around a file along with it.

#

I don't know what that looks like yet... maybe some additional flags for dagger.Connect or similar.

#

It has me curious where the latest thoughts around extensions are, @wintry cosmos, @frosty knoll, @tepid grove

tepid grove
#

I think it's all pretty up in the air, I've personally kind of put it on a shelf in my head for now

frosty knoll
#

Yeah I think that dagger.mod or equivalent would be needed at development time, but it should just be used for codegen. The code that's generated should encode the version of the extension that needs to be loaded. Then, since extension loading is just a part of the core api, they can load up the dependencies when they need to invoke them.

Of course, every single detail is up in the air, but that seems like one relatively simple path