-
Notifications
You must be signed in to change notification settings - Fork 817
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
fix(cli): moving the spinner above category initialization tasks #4836
Conversation
This pull request introduces 1 alert when merging 6959132d558f3029c86268b82dc25018bd62e24c into 79c774a - view on LGTM.com new alerts:
|
Codecov Report
@@ Coverage Diff @@
## master #4836 +/- ##
==========================================
+ Coverage 60.52% 61.25% +0.73%
==========================================
Files 350 349 -1
Lines 15203 15021 -182
Branches 2880 2858 -22
==========================================
Hits 9201 9201
+ Misses 5514 5332 -182
Partials 488 488
Continue to review full report at Codecov.
|
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.
LGTM bot alert made me realize the code can be simplified a bit
stopping the spinner before running category init tasks since the spinner can swallow outputs (such as questions via inquirer) re aws-amplify#4795
…-amplify#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks since the spinner can swallow outputs (such as questions via inquirer) re aws-amplify#4795
…-amplify#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks since the spinner can swallow outputs (such as questions via inquirer) re aws-amplify#4795
…-amplify#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks since the spinner can swallow outputs (such as questions via inquirer) re aws-amplify#4795
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
stopping the spinner before running category init tasks since the spinner can swallow outputs (such
as questions via inquirer)
related issue: sindresorhus/ora#90
re #4795
change type to intersection type in e2e
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.