Allow to configuring the date format for console output in watchdog:s… #6253
Conversation
| #[CLI\Option(name: 'severity-min', description: 'Restrict to messages of a given severity level and higher.')] | ||
| #[CLI\Option(name: 'type', description: 'Restrict to messages of a given type.')] | ||
| #[CLI\Option(name: 'extended', description: 'Return extended information about each message.')] | ||
| #[CLI\Option(name: 'date_format', description: 'Specify a date format for the date console output.')] |
There was a problem hiding this comment.
We typically use dashes in option names not underscores.
MaximeLemolt
force-pushed
the
allow-configuring-the-date-format-in-watchdog-console-output
branch
from
6bb4caa to
a7fce11
Compare
…ist and watchdog:show-one commands
|
@weitzman Yes, it was incomplete. I've made the necessary changes to allow the configuration of a date format for the “watchdog:list” and “watchdog:show-one” commands. I'm not sure if this is really necessary, but it meets a user need at a lower cost. |
|
One alternative is to use cell rendering to format the date instead of doing it in the formatResult(). That way json/yaml/csv outputs would not do cennrendering and would get timestamps. Those are presumably easier to consume for scripts. I'm not sure if that would help with your client need. This approach breaks backward compat for scripts unfortunately. Lets think about this a bit more. Sorry for the delay. |
Provide a solution for issue Resolve #6252