Loïc Rouchon

> First, thanks for pointing out the lack of a `Contributing` document. I just added one to the project. It's a first version, and suggestions for improvement this document are...

> One idea is to have a custom `generate-completion` command that (in its run method) invokes the built-in `picocli.AutoComplete#GenerateCompletion` command with the desired options. 👍 Ok, I'll write a test...

* Short option removed * `CommandLine` modifications reverted * host custom completion added (it's the same mechanism than the path one) Before moving forward with documentation and better test coverage...

Haha, don't worry about this, I totally understand your points and I know of experience things are easy until you get into details. Also here, it will impact the public...

Above force push was to fix the author email in the commits. Regarding the possibles solutions, I can't think of any other viable/acceptable ones for the moment. Looking at the...

Hello, no problem 😉 Here is some context for: _"Not centralized. To be repeated for every single @Option/@Parameters of the given type"_. I'm currently working on a project named [symly](https://github.com/loicrouchon/symly)...

> Reading your questions I got a strong sense that this approach (annotations on options/parameters) is the right approach. Still a lot to discover and flesh out, but this feels...

Hello @cbeams Yes, I would like to continue to work on this. At least on the narrow scope of the path/host completion for custom types. But the dynamic completion will...

So your proposal is to not have this information as part of the command spec, but to have it as a parameter when calling the `AutoComplete` command. Did I get...

Just a heads-up that I finally have some time to invest into fixing this issue. I made good progress today and I now need to write extensive tests for the...