New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support repeatable subcommands going up the hierarchy (was: I have a question regarding the subcommands) #1149
Comments
As far as I understand correctly it is a matter of not supporting "subcommands going up the hierarchy" that was asked about here: #454 (comment) If this is the case, would it be possible to enhance the picocli in a way that would allow for scenarios like the one posted above? It would be great to have this feature ;) |
@JavaDev99, @r2mzes's comment is correct. Currently picocli's repeatable subcommands do not support this. I will look into whether it is feasible to support this. |
I have this need too : #2133 |
Must-Have Feature I think a bit more about it and it seems to me that having a way to support You could answer that this is still possible to flattening the commands hierarchy OR massively use options but this often lead to ugly CLI in complex use cases. I feel this is like if GUI library doesn't allow you to create submenu (or submenu is allowed only as last element of menu) Something smelly with Current Behavior : I really think that current behavior is counterintuitive 🤔 . From CLI user perspective (I mean users who use CLI, not developers who use picocli library), it will be really hard to understand that he :
I feel it would be clearer to allow both OR forbid both. Imagine you have an image transformation tool. You can do :
But you can not do :
|
@sbernard31 sorry but I’m too swamped to work on picocli at the moment. For that last use case one idea is to add the |
Of course as a user I am disappointed 😞. I'm sorry if I seem too pushy but unfortunately users have only 1 power to impact project they depend on : discuss and provide argument hoping maintainer will agree.
Yep, but you need to :
Maybe you will succeed to have something OK from users point of view but now for sure your code is hard to maintain. |
Hi, @remkop, any news about that ? |
Hi @sbernard31, sorry but I cannot see myself working on this in the foreseeable future. |
@remkop, ok I understand. Eventually, if could try to work on it, if I do :
|
We are trying to implement this code
And we get the following error.
Could you tell us what solution may be for this
The text was updated successfully, but these errors were encountered: