-
Notifications
You must be signed in to change notification settings - Fork 93
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
cylc review: improve CLI #2928
Comments
IMO we should require an explicit argument to get server status, as I had assumed was the case: |
We can do this now with our own logic, or we can wait until we move away from |
(I've renamed this Issue to be more accurate given the previous comments.) I think it is best to wait until the Python 3 port is done, hence I will not assign myself & tackle it, but someone could always do so pre-migration if they wish. |
closing as wontfix. |
As outlined in #2924 (comment). For useful feedback we should notify users when any arguments passed have no influence on the code logic, particularly as I anticipate it could often be assumed a suite argument can be passed to this utility to open directly onto that suite's listing page, e.g:
The text was updated successfully, but these errors were encountered: