microsoft / microsoft/go-sqlcmd
Pick a shorthand switch for logging (-v is already taken for variables)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
A typical support scenario is going to be, can you run that command again with full logging, e.g.
sqlcmd create mssql -v 4
Which is currently short for
sqlcmd create mssql --verbosity 4
But:
-v is taken, -l is taken.
What's the POSIX CLI norm for getting full logging? (is --verbosity even a good flag name for this)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the sqlcmd create mssql command and review how -v, --verbosity, and -l are currently defined. Determine a POSIX-style shorthand and settle whether --verbosity is the appropriate name; done means the choice and its expected full-logging behavior are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100