-
Notifications
You must be signed in to change notification settings - Fork 184
fix(app): Show module setup screen on the Desktop app for the given module. #18487
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
- add setup another module button + logic to success screen - fix some screens that werent using the correct SmallButton vs PrimaryButton - blink module when we load the module setup launcher screen - add useSendIdentifyModule to new utils.ts file so we can reuse createLiveCommands - blink module red if install detection fails during module setup launcher - blink module blue when the device re-connects after a firmware update - stop blinking module when module setup is complete and the modal exits
…onally render them
- block moduleSetup exit when module is updating - stop blinking module if the flow is closed while in the SelectModule component - show the New Module Setup screen when launching module setup from the ModuleCard component - correctly start/stop blinking when retrying after InstallDetect failure
- Make sure we are correctly changing the LED state when setting up multiple modules
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## edge #18487 +/- ##
===========================================
- Coverage 57.47% 25.24% -32.23%
===========================================
Files 3269 3270 +1
Lines 280761 279640 -1121
Branches 33021 32981 -40
===========================================
- Hits 161355 70605 -90750
- Misses 119210 209007 +89797
+ Partials 196 28 -168
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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.
Nice thank you!
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.
Nice!
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 don't think we should add a current run poll to the top level like that - we're really trying to cut down on those. What if we instead check to see if there's a current run only when we recieve a module-connected event?
Agreed, however, the |
- dont return optional Null from JSX component, let the caller deal with conditonal rendering - dont define react components constants mid code, then use them in the return (render) function - replace console.error usage with setErrorMessage as these errors are non-recoverable for this flow + lets us get rid of returning null
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.
All right, sounds good to me!
Overview
Show the "Setup Module" screen when setting up a module on the Desktop app.
Closes: RQA-4208
Test Plan and Hands on Testing
Changelog
Review requests
Risk assessment
Low, unreleased