-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Guided onboarding] Implement quit guide functionality #142542
[Guided onboarding] Implement quit guide functionality #142542
Conversation
@kellyemurphy can you please review the copy in this PR? |
setIsDeleting(false); | ||
notifications.toasts.addError(error, { | ||
title: i18n.translate('guidedOnboarding.quitGuideModal.errorToastTitle', { | ||
defaultMessage: 'There was an error quitting the guide. Please try again.', |
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.
Do we want them to try again right away or should they wait a moment?
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.
Hmm... good question. I suppose it depends on the actual error. Do we have general guidelines around error messages when an API request fails?
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.
The error message guidance that we've provided the platform (cloud) team in the past is that we want to A. tell them what happened, B. tell them what they can do about it, and C. only use please when we are asking for their patience. This message meets those guidelines, but it's just a matter of timing.
src/plugins/guided_onboarding/public/components/quit_guide_modal.tsx
Outdated
Show resolved
Hide resolved
src/plugins/guided_onboarding/public/components/quit_guide_modal.tsx
Outdated
Show resolved
Hide resolved
…al.tsx Co-authored-by: Kelly Murphy <[email protected]>
…al.tsx Co-authored-by: Kelly Murphy <[email protected]>
…-ref HEAD~1..HEAD --fix'
Pinging @elastic/platform-onboarding (Team:Journey/Onboarding) |
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.
Thanks @alisonelizabeth, LGTM!
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.
Thanks a lot for implementing this functionality, @alisonelizabeth!
The UI changes LGTM but I'm not sure if we should delete the progress of the guide though. I thought when the use quits the guide, the state of the guided onboarding is set to something like "inactive" so that we know that the button is not shown in the header anymore. But if the user comes back to the landing page, they can see their previous progress on all guides. And they could continue a guide from the step where they left.
If we delete the state, I'm not sure how we would handle when the user comes back to the landing page and tries to restart a guide, wdyt?
That's a great question. @osmanis @cindychangy @bojanasan can you weigh in here? Based on the copy ("Quit this guide and discard progress?"), I thought the state would be discarded. However, I can't seem to find that in the design spec, so I might have made an assumption there 😅. If we do want to preserve the state, we should probably tweak the copy. |
Good catch, @yuliacech is correct that when a user quits the guide - it should save their state. We have a page on the prototype to show this situation. If a user re-visits the landing page they should see their progress of all the guides, and the buttons will show different text based on that ("View guide", "Continue"...). @alisonelizabeth: I agree given this, the copy should be tweaked as "discard progress" might be confusing if we are saving their state. @kellyemurphy do you have a suggestion on how to best tweak the title message: "Quit this guide and discard progress?". |
Thanks @cindychangy! For now, I've changed the modal title to simply: "Quit this guide?". @kellyemurphy let me know if you'd like me to make any further changes. @yuliacech would you mind taking another look when you have time? I updated the functionality via dc79bce. |
💚 Build Succeeded
Metrics [docs]Module Count
Page load bundle
History
To update your PR or re-run it, just comment with: |
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.
Thanks a lot, @alisonelizabeth! Latest changes LGTM 👍
I'm going to go ahead and merge this PR. I can follow-up with a separate PR if there are any additional copy changes. |
This PR implements the "Exit setup guide" functionality in the guide dropdown panel. Once the user confirms to quit a guide, an API request is made to delete the SO that is storing the guide's state.
Fixes #139804
How to test
kibana.dev.yml
file:guidedOnboarding.ui: true
yarn start --run-examples
/app/guidedOnboardingExample
/app/guidedOnboardingExample
the Search guide should say "Continue".Screenshots
// Loading state while API request is in progress