ada-magicat commented on issue #2150: URL: https://github.com/apache/buildstream/issues/2150#issuecomment-5079041891
> I can certainly see the verbose output being overwhelming for some users. However, it's not like BuildStream won't function with the verbose output for those users. This is obviously not about the tool functioning or not functioning, it is about the developer experience presented. > If the default verbose output is really confusing to a majority of users of particular projects, I'm wondering whether it might be reasonable to allow projects to define defaults for the user config. I.e., if the user doesn't explicitly set verbose in the config file and also doesn't pass --verbose or --no-verbose, use the project-defined default. > A project default for message-format could also be interesting. In my opinion, message-format is over-configuration, even in its current state. I basically know of no build tool that lets you do this, they all pick a good output format for what their use case is and if there are issues they improve on that. I really think buildstream should follow a similar approach of building a good default UX. There are also limitations of what message-format can even provide, of course. You actually can not use this feature to tell buildstream to not print certain kinds of messages, so I think it is not very relevant to this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
