-
Notifications
You must be signed in to change notification settings - Fork 74
Cannot specify a log level from the CLI #142
Comments
Agree, it would be a nice feature. It's a bit tricky to implement because we need a way to pass arguments to |
It might be as simple as looking for a logging.json so it can be configured externally. |
Assigning to @victorhurdugaci for invesigation in 1.1.0. |
Hey @glennc, what do you think about this one? |
hmmm. What are examples of the output that you want to suppress? Is it all output from watch? I am thinking a switch passed to watch to stop it from logging anything. |
Talked to @glennc offline. We'll make this configurable through and environment variable, just like we do for enabling the polling watcher. |
Here is an example from the DotNetCoreKoans project. The project is a teaching tool where the student is instructed to open the project in a text editor and then run When running the application without the watcher, I have complete control over the output. With the watcher, it clutters up the output making it hard to follow. At a minimum it would be nice to have the watcher respect a config file or a flag to specify silent output. |
Would we be still displaying errors in "quiet" mode, and just be silent otherwise? Or completely silent? |
The value you set in the env var will be the value from the LogLevel enum. If you set it to |
Hey @NotMyself , I added a new flag to allow you to turn off the log messages. See the updated readme for usage. |
In #197, we added We also removed the env variable added in #155. It's worth noting that #197 also added support for the global dotnet-cli verbose flag (usage |
I am attempting to write an interactive tutorial and want to use dotnet-watch. I would like to suppress the info messages printed out by the watch command so that only messages from my tutorial are displayed.
I have tried adding a logging.json file, but it doesn't seem to be respected. The log level in the Tools project appears to be hard coded to info. How can I override it?
The text was updated successfully, but these errors were encountered: