Determine the correct behaviour when a user requests limited output and debug
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
### Checklist
- [x] I have verified this is the correct repository for opening this issue.
- [x] I have verified no other issues exist related to my request.
### Is Your Feature Request Related To A Problem? Please describe.
_No response_
### Describe The Solution. Why is it needed?
Currently if a user requests limited output, in some places we emit the log to Debug instead of Info, and in others we don't emit anything. We should make a determination of which behaviour we want and then be consistent about it.
### Additional Context
_No response_
### Related Issues
_No response_
Contributor guide
Research direction
Start by determining the intended behavior when limited output is requested, including whether messages should be emitted at Info or Debug level or suppressed. Review the places where these behaviors differ, then define consistency across them and verify that the chosen behavior is applied everywhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100