-
Notifications
You must be signed in to change notification settings - Fork 374
feat: updated "Get started" flow available on every page #6365
Conversation
…oser into benbrown/getsmarted
remove get started from bot project settings page
chain modals togethert
beyackle
left a comment
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.
A few minor comments, but mostly this looks good.
| const hasLUIS = | ||
| botProject?.setting?.luis?.authoringKey && botProject?.setting?.luis?.authoringRegion ? true : false; | ||
| const hasQNA = botProject?.setting?.qna?.subscriptionKey ? true : false; | ||
|
|
||
| const hasPublishingProfile = | ||
| botProject?.setting?.publishTargets && botProject?.setting?.publishTargets?.length > 0 ? true : false; |
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'm wary of type-unsafe stuff like this, but in this case I think it's okay - I won't block the PR on it since I think there are no cases where those values could be real but falsey.
| "message": "Clear all" | ||
| }, | ||
| "click_start_and_your_bot_will_be_up_and_running_on_424c29da": { | ||
| "message": "Click start and your bot will be up and running. Once it’s running, you can select “Open in WebChat” to test." |
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.
Hooray for curly quotes in appropriate places!
Composer/packages/client/src/components/ManageQNA/ManageQNA.tsx
Outdated
Show resolved
Hide resolved
Composer/packages/client/src/components/GetStarted/GetStartedTask.tsx
Outdated
Show resolved
Hide resolved
| @@ -0,0 +1,680 @@ | |||
| // Copyright (c) Microsoft Corporation. | |||
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.
Agreed. It looks like ManageLuis and ManageQnA share a lot in common, so they could be refactored somehow.
) * Enable the get started widget to intelligently determine if LUIS or QNA is needed/configured * define nextsteps as an array that gets rendered * adjsut formating * move get started to top blue bar remove get started from bot project settings page * Add placeholder mvp luis keys modal * add placeholder mvp qna key modal chain modals togethert * introduce ProvisionHandoff component, to display customized instructions for creating azure components * luis widget * updated styles and content for get started * clean up code * add support for qnamaker provisioning * merge main * remove unused css * clean up unused vars * add final confirmation step to luis * updated ux for luis * fix button disabled state * ux fixes for luis * ux fixes for qna * magic teaching bubbs * cleanup * fix weird issue * Wrapping up UI for provisioning hand off modal * revised links and buttons in get started * remove unused styles * improve behavior of teaching bubbles during creation flow * highglight start bot when no steps are left * nav to page when opening modal * remove delete bot from settings page (still in toolbar) * make pane scrollable * delete unused ref * address issue with type mismatch in qna * fix mock * fix test * update syntax for accessing lufiles and qnafiles * address pull request feedback * locale * fix merge conflict Co-authored-by: Patrick Volum <pavolum@microsoft.com> Co-authored-by: Ben Yackley <61990921+beyackle@users.noreply.github.com> Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
Description
This is the first step of allowing the get started widget to intelligently display "Next steps" for a user
This detects the need for LUIS and QNA, then detects whether they are currently configured. This uses the same mechanism as the validation system.
Then, it displays "tasks" in the get started section.
EXPECTED BEHAVIOR:
The panel will only fly out at CREATE time, but the tasks will continue to be present
NOTE: Currently, tasks do not disappear once completed. We are investigating a method for doing this in a sensible manner.
INCLUDES:
Task Item
Fixes #6269
fixes #5827
fixes #6263
Fixes #5896
fixes #6364
fixes #6365
fixes #6546
Screenshots