Hey @open grove 👋 Just coming back. I had a sense you were working on something to make even bundled sdks be accessible via a git ref, or am I mistaken?
#SDK sources in runtime module
simple mauve
open grove
Hey <@949034677610643507> 👋 Just coming back. I had a sense you were working on...
No just proposed that we do that, not working on it at this time. Gonna talk about it in the prod-dev meeting on thursday https://github.com/dagger/dagger/issues/7585
simple mauve
Ah, that's it. Gonna read that carefully, thanks. Yeah, we need a solution to fix the current situation with experimental SDKs.
That issue doesn't seem to address the problem I just mentioned. It has to do with the runtime module having access to the SDK's sources. How do you suggest we fix that, other than contextual modules?
I'm thinking the simplest thing would be a simple convention of putting the runtime module in a runtime subdirectory of the sdk. That way the sources are the directory itself, without that subdir. So you'd point the --sdk to the path of sdk/php, for example rather than sdk/php/runtime.
somber rain
I'm thinking the simplest thing would be a simple convention of putting the runt...
I like the idea. I'm quite pain with Elixir SDK that the SDK source dir rely on git, I need to push the SDK fix into remote branch then start testing the runtime. 😢
With this idea, the New function just call CurrentModule().Source() to retrieve the SDK directory. So I can test the SDK api alongs with module runtime in the same commit.