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

feat(cmd/gno)!: change all -verbose flags to -v #1716

Merged
merged 3 commits into from
Mar 5, 2024

Conversation

thehowl
Copy link
Member

@thehowl thehowl commented Mar 1, 2024

Per the decision on #1555, we now have some exceptions for common scenarios where short flags make sense. gno test -v is super-useful as it connects to the muscle memory a Go developer has (with go test -v), so this PR adds it.

@thehowl thehowl self-assigned this Mar 1, 2024
@github-actions github-actions bot added the 📦 🤖 gnovm Issues or PRs gnovm related label Mar 1, 2024
Copy link

codecov bot commented Mar 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.41%. Comparing base (6c5b4cf) to head (a553abf).
Report is 3 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1716      +/-   ##
==========================================
- Coverage   47.41%   47.41%   -0.01%     
==========================================
  Files         384      384              
  Lines       61240    61230      -10     
==========================================
- Hits        29040    29030      -10     
  Misses      29771    29771              
  Partials     2429     2429              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@harry-hov harry-hov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you do this for other commands as well? (wherever it makes sense)

@harry-hov
Copy link
Contributor

what do you think about removing -verbose and just keep -v?

@thehowl thehowl requested review from a team as code owners March 4, 2024 20:56
@github-actions github-actions bot added the 🧾 package/realm Tag used for new Realms or Packages. label Mar 4, 2024
@thehowl thehowl changed the title feat(cmd/gno): add -v as an alias for -verbose feat!(cmd/gno): change all -verbose flags to -v Mar 4, 2024
@thehowl thehowl changed the title feat!(cmd/gno): change all -verbose flags to -v feat(cmd/gno)!: change all -verbose flags to -v Mar 4, 2024
@thehowl
Copy link
Member Author

thehowl commented Mar 4, 2024

@harry-hov bold, I like it :) done

Copy link
Contributor

@leohhhn leohhhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You've just shortened the testing time locally 😎

@thehowl
Copy link
Member Author

thehowl commented Mar 5, 2024

After posting this on signal, there seems to be an overwhelming consensus to do this, so going ahead and merging :)

@thehowl thehowl merged commit 27c5a65 into master Mar 5, 2024
191 of 193 checks passed
@thehowl thehowl deleted the dev/morgan/gno-test-v branch March 5, 2024 12:21
thehowl pushed a commit that referenced this pull request Mar 5, 2024
leohhhn pushed a commit to leohhhn/gno that referenced this pull request Mar 6, 2024
BREAKING CHANGE: `-verbose` is no longer a flag recognised by any
command. All its usages should be switched to `-v`.

Per the decision on gnolang#1555, we now have some exceptions for common
scenarios where short flags make sense. `gno test -v` is super-useful as
it connects to the muscle memory a Go developer has (with `go test -v`),
so this PR adds it.
leohhhn pushed a commit to leohhhn/gno that referenced this pull request Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 🤖 gnovm Issues or PRs gnovm related 🧾 package/realm Tag used for new Realms or Packages.
Projects
Status: Done
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants