-
Notifications
You must be signed in to change notification settings - Fork 207
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
Effy small UI polish #411
Effy small UI polish #411
Conversation
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 css for the gradient? The image seems unnecessary and adds to the package sizes.
packages/web/src/routes/home.tsx
Outdated
|
||
useEffect(() => { | ||
const checkApiKey = () => { | ||
const hasSeenOnboarding = localStorage.getItem('hasSeenOnboarding') === 'true'; |
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 should live in persistent storage (sqlite), at least in the medium-long term.
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 updated this logic to instead gate on whether aiEnabled
being outputted from useSettings
was enabled rather than segregating the onboarding state individually.
I don't think there's a reason that tracking this separately is important, given that this should be shown for all users that don't have an ai api key set - if so though, please call it out.
cdf0bca
to
6c090a6
Compare
…d reuse existing ai key management code
3a91045
to
8b2900c
Compare
Adds a new onboarding screen which gates a user from visiting the application's home page until they've added an ai api key: