-
-
Notifications
You must be signed in to change notification settings - Fork 621
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
chore: fix and refactor add generator #843
Conversation
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.
IMO this might affect node 6.x users.
Node supports async/await out of the box since version 7.6.
Refer #836 |
Ready for a review now 👍 |
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.
I'll do some manual testing while I got time, but nice work.
packages/generators/add-generator.ts
Outdated
} | ||
} | ||
|
||
const temp: string = action; |
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.
reassigning a const
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.
Where? temp is never reassigned anywhere and here it is declared.
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.
Left some feedback!
Thanks for review @ematipico P.S |
Oh yeah don't worry! We know it's working all right, if you think it doesn't require any change and it will steal too much time of yours, mark it as resolved and move along. :) |
Well all are done and it didn't steal my time :). Pushing commits after a quick test. |
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Done @evenstensberg |
@webpack/cli-team can I have a review on this PR, this is fine IMO |
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.
Seems good to go!
@evenstensberg PTAL 😅 |
Thanks, will get back to you this week. Quite a big PR and need to manually test |
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.
Triaging #817 first to avoid complication of work
@rishabh3112 could you rebase and let's continue on getting this merged once you're done? |
Sure, will catch you tommorow. It's night here now and I am sleeping :) |
Gotcha, sleep tight! |
@rishabh3112 Thanks for your update. I labeled the Pull Request so reviewers will review it again. @anshumanv Please review the new changes. |
Could you rebase? |
Will do it @evenstensberg, but is it required now?, as add package is being removed Or we would keep generators and remove packages only? |
Nah I don't think it's worth |
What kind of change does this PR introduce?
refactoring
Did you add tests for your changes?
No
If relevant, did you update the documentation?
N/A
Summary
Updating
prompting()
to use async/awaitDoes this PR introduce a breaking change?
Maybe
Other information
#836