-
Notifications
You must be signed in to change notification settings - Fork 823
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
fix(permissions): macos ux improvement #1279
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
why is there 26 file changes? this should be like 3-4 files not more keep it simple |
@louis030195 ik.. most of those changes are just reorganizing files for better dx:
Its just that while debugging onboarding it was hard to understand its flow, lots of places controlled dialog visibility and user input state. For example, showOnboarding was being set in three different components for different reasons which made onboarding not reopen consistently upon restarting the app core logic remains the same with the changes its now really easy to understand when and why showOnboarding is set to false, dialog will reopen at permissions slide when restarting for screen recording permissions |
return type of permissions is string, always true. check should be similar to onboarding's status
- moved file into @/components/onboarding - renamed onboarding.tsx to dialog.tsx final result @/components/onboarding/dialog.tsx
- move into @/components/onboarding - rename from use-onboarding to context final result: @/components/onboarding/context
- move all slides from @/components/onboarding to @/components/onboarding/slides
…ons after "request_permission" is invoked this gives user and system time to grant permissions before we trigger a check. Otherwise, function checks prematurely
- use localforage to set showOnboarding - make functions asynchronous
@oliverqx is attempting to deploy a commit to the louis030195's projects Team on Vercel. A member of the Team first needs to authorize it. |
- was previously using LAST_AUDIO_CAPTURE from screenpipe-audio/core line 16 which is essentially just a SystemTime::now(). Now using response from state.db.get_latest_timestamps. - lowered threshold from 1 hour to 2 minutes. Seems like if not disabled, the user wouldnt want to wait 1 hour before being notified that nothing is being recorded
…ermissions are broken
@louis030195 I think this is ready to be reviewed. I know its a lot but here's a quick overview of what I've done:
id be down to schedule a quick meeting to go over the changes if necessary |
restart is handled in useOnboardingVisibility hook
/claim #1273
/claim #1264
description
this pr will address the following issues: #1273, #1264
goals