You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the dotnet CLI uses a basic Reporter class that is used to output to the console. This is a very basic outputter and doesn't offer any shared logic or functionality for the commands to utilize. We've added other aspects around it to help with code reuse, but we need several mechanisms to kinda "heard the cats" on output from the CLI in general.
High-Level Changes/Goals
Allow built-in filtering mechanism for different output levels (built-in "verbosity" concept)
Allow different output formats (machine-readable formats included)
Allow better support for help text (currently very haphazard, only basic support from S.CL)
Allow output to include both stdout and stderr
Review all current command outputs and integrate these consistency features
QoL: Built-in coloring and resource string support
Potential: Native recognition of S.CL options (such as verbosity, output formats, help) to work with the features above
Potential: Consider design for the interactive prompt experience as it relates to output
The text was updated successfully, but these errors were encountered:
Summary
Currently, the dotnet CLI uses a basic
Reporter
class that is used to output to the console. This is a very basic outputter and doesn't offer any shared logic or functionality for the commands to utilize. We've added other aspects around it to help with code reuse, but we need several mechanisms to kinda "heard the cats" on output from the CLI in general.High-Level Changes/Goals
The text was updated successfully, but these errors were encountered: