-
Notifications
You must be signed in to change notification settings - Fork 27
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
let's have the most useful output! #65
Comments
@TomasTomecek I have no problem with that..;-) Only using the tool gives us the right answer to design. |
One idea to that topic -- I personally don't like the WARN/ERROR log messages shown by default. I think the regular user does not need to see that. (Only the last line with one line error description.) |
@lachmanfrantisek I agree; would you be interested in adding a real output here so we can see how it could look? |
--->
-->
|
I've changed Actual state:
|
@lachmanfrantisek Would it be possible to remove spaces between release and description / message. Not like [EDIT] I don't know if it makes sense. |
@phracek Isn't it less readable?
|
One another question: Do we want (I am thinking about printing logs only in the |
This is something I deeply care about that why I'm such a PITA about it.
After I tried colin recently, I was overwhelmed by the output: there was too much info for me and it wasn't easy to read. One suggestion I have here is to color only lines such as
nok:failed:bzcomponent_deprecated
and not the description.The other thing I'm thinking about is the line itself; would it be better to have something like this?
Since we have almighty @jpopelka on our team now, I have an idea: Jirko, would you be so kind and played with colin a bit a tell us your opinion about the output and your user experience?
Franto, I understand if you are now like "what the funk is this guy's problem", but as I said, I would love if colin had an awesome output which suits everyone and the tool is such a pleasure to be used. I think we are heading there, I just want to make sure we get there. Happy Friday!
The text was updated successfully, but these errors were encountered: