#14 closed enhancement (fixed)
Revamp --status output
Reported by: | Max | Owned by: | Max |
---|---|---|---|
Priority: | minor | Milestone: | 1.0 |
Component: | Shepherd | Version: | 0.3 |
Keywords: | Cc: |
Description
From email discussion...
Max:
Speaking of which, I wouldn't mind seeing a revamp of that output. The
grabber descriptions should probably only be displayed if requested via something like --desc... it's kinda pointless to print that out all the time. Similarly, grabber quality probably belongs in a --desc output, not --status. But grabber version could be significant so I think should go back in the main --status table.
It would also be nice if "Last Run" output the time of day rather than
date when date == today.
Oh, and I don't really like the grabber's status being overwritten when
the version updates. You lose important info that way.
Whaddya think?
Lincoln:
indeed, i think it can do with a fair revamp:
- last ran: should be stored in epoch time so we can use a sliding scale (if today, just list time) if yesterday say yesterday + time if within last 2 weeks say "n days ago" etc
- there's really two types of status:
- status from running it (& whether it succeded)
- when last changed (admin/operational) - eg. auto-updated, enabled, disabled, update to version X.Y is pending on install of module blah, etc.
Change History (2)
comment:1 Changed 16 years ago by
Owner: | set to Max |
---|---|
Status: | new → assigned |
comment:2 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Mostly addressed by [368]. We could still split up that status output.