Thanabodee Charoenpiriyakij
Thanabodee Charoenpiriyakij
@TomChv I’ll waiting for that PR to be merged then. :)
Rebased the change. Would you like me to add a test?
> #### Install a client > dagger client install GENERATOR [PATH] [-n|--no-generate] What can GENERATOR be? I imagine that: 1. A built-in, go, typescript, python and including experimental, elixir, java...
Will looking for Elixir within today✌️
Let's demo using PowerShell Core: First, let bootstrap intrspection file with `dagger call -m dev introspect export --path=sdk/Dagger.SDK/introspection.json`. Then execute commands below to run the pipeline: ```powershell wingyplus@WINGYMOMO ~/s/g/d/d/s/d/sdk (sync-dotnet-sdk)>...
@helderco The DCO is fixed. And I do squash all commits into a single one. See the `testdev` failure but never get it success. I'm not sure why. T_T
Retry and all pass!
> Heads up that we'll want every SDK to implement codegen using Go, after we clean that up. In the meantime, this is ok. Excited to see how’s it work....
> Ideally we should version-compat this change - it has the potential to break published modules, so should have a check here. I’ve never dealing with a version compat before....
> @wingyplus see https://github.com/dagger/dagger/pull/9118/files#diff-8062ad596c2b352a00e64f30eb9fff7ade878660570bf2c3c5f5aa727dd10496R864 for an example of where I've done this recently. > > Generally: > > * If a core function signature changes, you use [dagql views](https://github.com/dagger/dagger/blob/e2be4eaedc36f1c65efcff760cae4d596e323b82/core/schema/container.go#L335-L336) >...