Vasek - Tom C
Vasek - Tom C
## Context I'm learning postgREST so it's maybe my fault but then I'll certainly open a PR to update doc regarding to my issue. I'm trying to create a REST...
## Changes Fix typo in the README.md
When https://github.com/dagger/dagger/pull/1839 will be merged, we should update this action to supports cache option. In a discussion with @aluzzardi, we talk about the following shape: ```yaml name: Dagger uses: dagger/dagger-for-github@v2...
Enforce prettier rules and install sort import plugins. Cleanup codebase. Update Eslint's' no-unused-vars' rule to allow '_'. Fix code duplication between image.ts and bin.ts. Signed-off-by: Tom Chauveau
### What are you trying to do? I want to find an elegant way to handle error globally without any code duplication ### Why is this important to you? It's...
Dagger plan always follows the same logic: 1 - Define your action 2 - Create or call definition To improve user experience, we could integrate code snippet in the LSP,...
It's common for a LSP to integrate file formatting, Dagger LSP should not be an exception. When user press command to format file, Dagger LSP should execute `cue fmt` function...
The next step after #42 is dynamic completion. For example, if a definition `#Foo` is written in the plan, when the user type `#Fo`, Dagger LSP should propose `#Foo` and...
As a LSP, it's primordial to enhance user productivity through multiples helpers. One of them is the completion. It's a really strong tool that helps write things faster and reduce...
That would be useful to see how a value is constructed. For instance ```cue #Definition: { foo: string } #Embed: { #Definition bar: number } ``` Will produce the result...