-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: fix CLI execution with explicit --controllerType=BASIC option #10624
base: master
Are you sure you want to change the base?
fix: fix CLI execution with explicit --controllerType=BASIC option #10624
Conversation
Hi, @major-winter. Can you please add some tests around your change? The changes looks good to me. |
458ddc1
to
bb42e57
Compare
Hi @aaqilniz , I've undone as suggested. Please review the PR again. Thank you for your support. |
Hi, @major-winter. Please squash the commits. Everything else seems good. |
…ASIC - fix CLI execution with explicit --controllerType=BASIC option - add a unit test that verifies the scaffold when explicity specifying the controller type as BASIC Signed-off-by: TC <tuanchuhoang@gmail.com>
bb42e57
to
c50e1df
Compare
Hi @aaqilniz, I've squashed my commits into 1. Please review it when you have time. |
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
fix #10494
Fix controller failure when --controllerType=BASIC is explicitly specified
Checklist
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈