Open dsawardekar opened 2 months ago
Attention: Patch coverage is 40.81633%
with 29 lines
in your changes missing coverage. Please review.
Project coverage is 63.0%. Comparing base (
766e351
) to head (b3d8730
). Report is 319 commits behind head on feature/2458-streamline-onboarding.
@joemcgill This is working but I needed to move the implementation to the parent container component. Having the logic inside the SavedSetupStepper was causing a broken UX like below when the user already had completed store requirements.
Can you review and let me know if this looks good to proceed on the e2e tests?
Thanks!
@joemcgill I've added the e2e tests for this, but I need assistance with mocking the email and mc account address. When I try to set mockMCSetup to use 'complete', it redirects to the Home page, and skips the onboarding flow completely.
Can you please take a look? Thanks!
@joemcgill That might work, but the UX would be less than ideal. Maybe we need to consider folding the things that in that extra dissapearing step into sections inside Step 2 / 3. Then if the user has sufficient data, we could hide that section.
Changes proposed in this Pull Request:
Closes #2493
This PR hides the confirm registration step if the user has sufficient data filled in already. If the user was on the confirm registration step previously, they are sent to the next step.
Screenshots:
With incomplete store requirements: (Confirm store requirements is present)
With complete store requirements: (Confirm store requirements is absent)
Detailed test instructions:
Additional details:
Update: Hides the Confirm Store Requirements step when feasible
Changelog entry
Update: Hides the Confirm Store Requirements step when feasible