Tanguy ⧓ Herrmann
Tanguy ⧓ Herrmann
### What is the issue? I want to use the new errors from the NodeJS SDK v0.3.0, but I don't know how to access it. It seems they are not...
### What is the issue? Since now we split required args and optional args, we need to update the code in the documentation. Other breaking changes might have to update...
### What is the issue? Sometimes, their names are explicit enough, sometimes, they are not eg.: https://pkg.go.dev/dagger.io/dagger#ContainerOpts What is a platform? What's its format? Going to https://pkg.go.dev/dagger.io/dagger#Platform doesn't give more...
For now, the templates used by the NodeJS codegen are not documented. It's hard for a newcomer to know what to modify in those templates. We need to document that.
based on https://github.com/dagger/dagger/pull/3606#issuecomment-1319309884, we need to refactor the Go codegen to make it more coherent with the NodeJS one. cc @aluzzardi
The github action https://github.com/dagger/dagger/actions/runs/3553457291/jobs/5968980250 which handles the issues backlog failed with ``` Projects cannot have more than 1200 items. To add more, please archive or delete existing items. ``` _Originally...
There is a companion plugin to vim-lsp that automatically creates configuration for vim-lsp. We should add our contribution: [mattn/vim-lsp-settings](https://github.com/mattn/vim-lsp-settings) Then we won't have to create configuration documentation other than >...