Skip to content
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

Jump to bottom

Setting for always using verbose logs #1940

Closed
Trenly opened this issue Feb 15, 2022 · 0 comments · Fixed by #1945
Closed

Setting for always using verbose logs #1940

Trenly opened this issue Feb 15, 2022 · 0 comments · Fixed by #1945
Labels
Area-Settings Issue-Feature Resolution-Fix-Committed
Milestone
v1.3-Client

Comments

@Trenly
Copy link
Contributor

Trenly commented Feb 15, 2022

Description of the new feature / enhancement

As a user of the pre-release versions, I would like all commands to be logged verbosely without having to specify --verbose-logs

Proposed technical implementation details

Add a setting for this
@Trenly Trenly added the Issue-Feature label Feb 15, 2022
@msftbot msftbot bot added the Needs-Triage label Feb 15, 2022
@Trenly Trenly mentioned this issue Feb 16, 2022
Merged
2 tasks
@msftbot msftbot bot added the In-PR label Feb 16, 2022
@msftbot msftbot bot added In-PR and removed In-PR labels Feb 17, 2022
@msftbot msftbot bot added Resolution-Fix-Committed and removed In-PR labels Feb 17, 2022
@denelon denelon added this to the v1.3-Client milestone Jun 21, 2022
@Trenly Trenly mentioned this issue Jun 30, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Settings Issue-Feature Resolution-Fix-Committed
Projects
None yet
Milestone
v1.3-Client
Development

Successfully merging a pull request may close this issue.

Setting for Logging Level Trenly/winget-cli
2 participants
@Trenly @denelon