-
Notifications
You must be signed in to change notification settings - Fork 152
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
feat(android-setup): Create three state machine steps #2865
Conversation
@@ -7,6 +7,6 @@ export const detectAdb: AndroidSetupStepConfig = deps => ({ | |||
actions: {}, | |||
onEnter: async () => { | |||
const detected = await deps.hasAdbPath(); | |||
deps.stepTransition(detected ? 'detect-devices' : 'prompt-locate-adb'); | |||
deps.stepTransition(detected ? 'prompt-connect-to-device' : 'prompt-locate-adb'); |
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.
Confusion here was because it wasn't clear what hasAdbPath was doing. I read it as "is there a path in the store" when it really means "Do we have a validated ADB location?" The underlying code will decide based on whether or not the AndroidServiceConfiguratorFactory was able to return an AndroidServiceConfigurator
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.
Please see my comments in detect-adb.ts
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.
Should rename hasAdbPath to something that more clearly identifies its internals
Description of changes
The new steps are:
Pull request checklist
yarn fastpass
yarn test
)<rootDir>/test-results/unit/coverage
fix:
,chore:
,feat(feature-name):
,refactor:
). SeeCONTRIBUTING.md
.