-
Notifications
You must be signed in to change notification settings - Fork 31
Switch System.CommandLine to Spectre.CLI #920
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
Conversation
ff3e778
to
284eaff
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/net8-upgrade #920 +/- ##
=======================================================
Coverage ? 62.34%
=======================================================
Files ? 294
Lines ? 10736
Branches ? 1559
=======================================================
Hits ? 6693
Misses ? 3484
Partials ? 559 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
531f785
to
96e5ca8
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.
do we use spectre cli for our other projects? whats the reason for this change?
Yes we started using it in the new Test Tool. It is more feature rich and allows for a lot of CLI customization and interactivity. The current one we were using hasn't been updated in years and it's still in beta. |
Issue #, if available:
DOTNET-8095
Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.