-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
DISCUSSION: Improve our existing CLI commands in Flow/Neos #5128
Comments
Assuming you want to open a general discussion about Flow CLI commands, here's my take: I would like to see the introduction of global flags which can be used in any command. For starters, it would be great if you could do just append Another type of flag I'd love to have is Other than that, I don't like the pattern That's what I'd love most regarding commands at the moment. |
I really like the pattern of |
Another thing I would personally really want to do long term is use symfony/console parsing of arguments, so it would be great to not add anything that contradicts that if possible. |
But that's just what we have now, or what do you mean?
I think that this is quite inconvenient, because I often start writing a command like so:
and then wonder which other flags exist. So I have to go all the way back between And without going into detail, there are quite a few technical and aesthetic issues I have with |
Right, I forget we do have that. It seems to be a pattern many tools follow though, so it's at least well known? But I am fine if we shift to global |
Hello @robertlemke & @kitsunet Thanks for your feedback!
I totally see your point. I also work with other CLI tools and there its the same schema/behavior that you have a Bildschirmaufnahme.2024-06-05.um.15.53.59.movRight now i'm a bit unsure about this. Would it make sense to have one PR that contains the changes with the |
Personally, I'd keep the pull requests as small and focused as possible – create one which introduces the But I guess we shouldn't change the old behavior (yet) that if you specify no arguments or miss arguments ( One topic I completely forgot which also need improvement: In my opinion, Flow should throw an error and exit with a code != 0 if you specify an argument which does not exist. Imagine you have a |
👍🏽 I was just about to create a DRAFT PR for it, but then I realized that there is no 8.4 branch in the
Totally agree |
Is there an existing issue for this topic?
Description
Hi,
I have been working with commands for the console for a while now and have found it interesting!
Therefore, I would like to take on the topic of improving our existing CLI commands if necessary.
In the last few weeks, I have been thinking about what new commands could be introduced. But so far I haven't come up with anything useful. But we already have a whole range of CLI commands. So I would like to concentrate on improving our existing ones.
But of course, you can also contribute your feedback for new commands if you have something in mind!
I look forward to your feedback!
Open issues
Open Pull requests
Possible Solution
No response
The text was updated successfully, but these errors were encountered: