-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add code info cli command #106
Comments
@treeder please check out output
|
I'm thinking about similar function for tasks and schedules. |
added arrow before 'Code package...'
|
Per @iced 's suggestion:
|
@romand-ironio see modifications below .. thoughts?
|
@treeder I think we can introduce autodetection of argument here. We can try to interpret 'info' argument as:
|
That's interesting. I suppose API would need an endpoint to take any ID and figure out what it is? |
we can try all options in CLI, no need in separate API call |
Ahh, I see. I think it would best to be explicit then, slow/wasteful to try 3 times for each request. Let's stick to the |
@treeder extra requests doesn't seem to be bottleneck here
@iced what is your opinion? |
info code XX |
@evan to implement schedule info command properly, list of possible fields returned by API along with situations when they appear needed as I can see from hud source code, following fields are available:
Are all those fields exposed to API response literally? |
|
TODO: |
done |
Usage:
Would return:
The text was updated successfully, but these errors were encountered: