-
Notifications
You must be signed in to change notification settings - Fork 113
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
Feature Hint cards and app walkthrough #1454
Conversation
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
agree we need some UX + UI improvements here |
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
Signed-off-by: Tynan DeBold <[email protected]>
…ature/app-onboarding Signed-off-by: Tynan DeBold <[email protected]>
Thanks Tynan! Some notes:
|
…ent; rest of the logic and dot adjustments Signed-off-by: Tynan DeBold <[email protected]>
Thanks for a thorough review @stephkaiser! I've addressed all your comments now. Feel free to check things again :) |
Signed-off-by: Tynan DeBold <[email protected]>
looks awesome! @tynandebold no comments from me :) |
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.
@tynandebold this looks good.
For the first card - If you select the dataset and click Expand Preview Table, The page opens showing the datasets but also the yellow indicator as seen below:
This is a similar experience with the second card when you select 'Price Histogram' and select 'Expand Plotly Visualisation' the yellow indicator is still shown as seen below:
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.
Awesome work !! I have left few comments, nits and questions. I feel neither of them is a major blocker. Approving the PR. Thank you
package-lock.json
Outdated
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.
is this change required ?
learnMoreLink: | ||
'https://docs.kedro.org/en/stable/visualisation/visualise_charts_with_plotly.html', | ||
elementId: '.pipeline-node__bg--plotly', | ||
image: |
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.
can we use image location instead of image data string ? something like - "imageLocation": "../static/images/plotly.png"
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.
Currently we don't have a mechanism that allows us to bundle static images in Viz. We'd need to account for the potential of the path changing in local development versus production, too.
Something to investigate for the future.
{featureHintsContent[featureHintStep].image && ( | ||
<img | ||
alt={featureHintsContent[featureHintStep].title} | ||
src={featureHintsContent[featureHintStep].image} |
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.
Can we change the text image content and instead have some kind of url src ?
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.
See my comment above about this.
} | ||
|
||
.button button { | ||
color: colors.$black-900; |
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 could not understand why we use #{colors.$black-100}
sometimes like string interpolation and sometimes access direct value like colors.$black-100
. What is the major difference regarding the usage ?
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 use it consistently. String interpolation of this kind is only needed when you want to use the variable somewhere it isn't allowed.
description={settingsConfig['showFeatureHints'].description} | ||
onToggleChange={(event) => { | ||
setShowFeatureHintsValue(event.target.checked); | ||
setHasNotInteracted(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.
why do we need setHasNotInteracted ?
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.
This is the state variable that changes the submit button from disabled to active.
Nice catch @NeroOkwa . When someone is in the tour, should we disable/not allow the users to interact with the app or make changes ? @tynandebold @stephkaiser |
Signed-off-by: Tynan DeBold <[email protected]>
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.
LGTM 🚀
Description
Resolves #1180.
Development notes
I've added what I'm calling the
AppOnboarding
component and necessary files. I'm opening the PR a little early to get it into our hands so we can test it out. I feels suboptimal right now.QA notes
Screen.Recording.2023-07-17.at.19.39.28.mov
Look at the Gitpod link and play around with it and reference the design here.
I think there's a wrinkle or two with the concept itself. See my comment here for more details: #1180 (comment).
Other things that we can improve:
Still todo from the dev side:
Checklist
RELEASE.md
file