-
Notifications
You must be signed in to change notification settings - Fork 80
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
#1682: fix unit tests #1734
base: main
Are you sure you want to change the base?
#1682: fix unit tests #1734
Conversation
19d4abb
to
7453642
Compare
7453642
to
e4b3254
Compare
e4b3254
to
2b58f20
Compare
What needs to merge before this PR can be merged? |
@leighmcculloch we can either merge all listed PRs at the same time or merge all of them here first |
This is looking great! Thanks for digging into it - it was driving me crazy ;p
W/r/t when to merge this and the other PRs, i like the idea of merging those test fixing into this PR first. |
Co-authored-by: Elizabeth Engelman <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for figuring out why these tests were preventing from running. Great find and learning for us all.
For the solution, I'd like us to reconsider the approach here, see the inline comment. Please lmk if there's a reason we can't do the error approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One ask, otherwise this looks good, very easy to follow.
* Fix init test * Update sdk version
* fix config tests * Fix version test * fix: clippy --------- Co-authored-by: Willem Wyndham <[email protected]>
* Fix build tests * revert implementation
d26395b
to
ed53892
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good to me, besides @leighmcculloch 's comment about moving the HelpMessage switching to the top level. I wonder this PR can go in as-is, and that can be a follow up PR?
I'm also curious what the exit code should be when no --help
flag is passed. I am currently seeing that scenario, as well as when a --help
is passing both returning a 0 error code.
7a0c827
to
80daeb7
Compare
92a021a
to
da1dd35
Compare
da1dd35
to
da763ed
Compare
Part of #1682
Fixes unit tests, including restoring
help
testsWhy
Previously, we were using clap's
get_matches_from
that exits with code 0 (printing help message). This made our tests exit with code 0 as well (when calling--help
).As part of the change we handle
DisplayError
returning help message, and keeping existing behavior for all other clap errors.Known limitations
Some win tests are failing