@Helder Correia would you consider | Dagger | Page 1

frosty pewter Mar 13, 2024, 7:43 PM

#

This is an awesome idea, how do we make it a reality? 😄

related: #java message

shy yew Mar 13, 2024, 9:10 PM

#

I don't how how to make it "mini" 🙂 It takes a bit of work.

frosty pewter Mar 13, 2024, 9:13 PM

#

Id sign up for the mega version too

shy yew Mar 13, 2024, 9:21 PM

#

We could do something basic, like only supporting primitive types. But we'd need a simple language that's easy to extract the typing information from, and it's best if there's already a codegenable client so we don't have to deal with that first. Python actually fills all of that, so it's possible to make an MVP in Python from "scratch", to show the basics of how to support modules.

#

I'm assuming modules, but if it's a new SDK, codegen isn't easy enough for that yet and you have to create the client.

#

I'm thinking for new SDK's it would be cool to start with supporting modules, using raw queries in the function body, and create the client after that.

#

I actually have a new language in mind for a new SDK which can be used as a model/example for new SDKs, but I'm waiting for some basic introspection/reflection/ast features to be able to start.

hazy kestrel Mar 14, 2024, 12:51 AM

#

👀 👀 👀 👀 👀

#

My candidate is a docker-compose SDK 🙂

#

Where the docker-compose services are exposed as functions directly

#

And each service type gets its own Dagger type

#

Arguments can be inferred from environment variables passed to the service container

#@Helder Correia would you consider