#Hi Justin, would you have some time to

1 messages · Page 1 of 1 (latest)

undone coral
#

I am trying to base my changes on how dependencies are managed for a module (assuming sdk is kind of a dependency as well)

#

but seems like in some areas of code, that assumption may not be right

undone coral
#

e.g. for go sdk, there is no dagger.json

#

I am thinking instead of this being a ModuleConfigDependency, shouldn't this be a *core.SDK instead (or some shape of it as *core.SDK is an interface)?

stable fulcrum
#

for go, it would probably just be {name: go}

#

and similar for python+typescript

#

but for external sdks, it should probably have source + pin as well

#

i.e. following dependency as much as possible