I am exploring the generation of CLI

[teal crag]

We're not planning on changing how args work dramatically.

The biggest change is that we're working on centralizing everything to a single command: https://github.com/dagger/dagger/issues/6229

I think if you start out by just generating examples for simple cases that use dagger call, that would probably be relatively safe. I just would avoid going too deep into generating examples for dagger shell/dagger up/etc.

[median portal]

Perfect, thanks 🙏

[median portal]

I am having trouble with the Container type argument:

dagger call -m github.com/sagikazarmark/daggerverse/helm@93e0edf41a5d1176f382dd295c528c1d8f71803e from-container --ctr  docker.io/library/alpine:latest      
                    
✘ dagger call from-container ERROR [0.00s]
┃ Error: "from-container" requires a sub-command                                                                                                                                                              
┃ Run 'dagger call from-container --help' for usage.                                                                                                                                                          
• Engine: a8ed07519657 (version v0.9.5)
⧗ 1.62s ✔ 34 ∅ 6 ✘ 1

Where : --ctr is of type Container. It seems that the arg is not recognized ?

--
Oh, but this works:

dagger call -m github.com/sagikazarmark/daggerverse/helm@93e0edf41a5d1176f382dd295c528c1d8f71803e from-container --ctr  docker.io/library/alpine:latest   container

Meaning that if a module returns another module, we need to satisfy the conditions of the returned module in the exec of the CLI ? Is that how we know that it requires a subcommand ?

Or, is the heuristic: if a function returns another module, a subcommand from that given module is expected