Skip to content

Toggle Active Sync to test Background Sync #3122

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

Merged
merged 4 commits into from
Jun 19, 2025
Merged

Conversation

DennieDan
Copy link
Collaborator

@DennieDan DennieDan commented Jun 19, 2025

Notice that the default settings is isActiveSyncOn=false so non-tuturuuu.com account by default now don't have active sync. This is meant for us to test the backgroundSync easier.

If required, I can change the default to isActiveSyncOn=true

Copy link
Contributor

coderabbitai bot commented Jun 19, 2025

Walkthrough

This update introduces the ability for users with "@tuturuuu.com" email addresses to toggle an "Active Sync" feature for Google Calendar synchronization. It achieves this by extending the calendar sync context and provider with new state and control logic, and conditionally rendering the toggle in the Google Calendar settings UI. Additionally, type declarations for database functions are reorganized and slightly extended for consistency.

Changes

File(s) Change Summary
packages/types/src/supabase.ts Reordered and grouped properties in argument and return types for various database functions; added new optional/required properties to certain argument types; no changes to underlying data types or semantics.
packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx Added logic to detect "@tuturuuu.com" users and conditionally render an "Active Sync" toggle; integrated with new calendar sync context properties.
packages/ui/src/hooks/use-calendar-sync.tsx Extended context and provider to include isActiveSyncOn state and setter; updated sync logic to respect this state; exposed new properties in context; added effect to trigger sync when toggled on and data is valid.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GoogleCalendarSettings
    participant useCalendarSync (Context)
    participant Supabase

    User->>GoogleCalendarSettings: Open Settings
    GoogleCalendarSettings->>Supabase: Fetch authenticated user info
    Supabase-->>GoogleCalendarSettings: Return user email
    GoogleCalendarSettings->>GoogleCalendarSettings: Check if email includes "@tuturuuu.com"
    alt Tuturuuu user
        GoogleCalendarSettings->>User: Render "Active Sync" toggle
        User->>GoogleCalendarSettings: Toggle "Active Sync"
        GoogleCalendarSettings->>useCalendarSync: setIsActiveSyncOn(newState)
        alt isActiveSyncOn becomes true
            useCalendarSync->>useCalendarSync: Trigger syncToTuturuuu()
        end
    end
Loading

Possibly related PRs

Suggested labels

enhancement, calendar

Suggested reviewers

  • vhpx

Poem

In the warren where calendars hop and sync,
A toggle now lets Tuturuuu users think:
"Should I keep my sync alive,
Or pause and let my plans survive?"
With types reordered, neat and bright,
The rabbits code through day and night!
🐇⏰✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/types/src/supabase.ts

Oops! Something went wrong! :(

ESLint: 9.29.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@typescript-eslint/parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx

Oops! Something went wrong! :(

ESLint: 9.29.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@typescript-eslint/parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

packages/ui/src/hooks/use-calendar-sync.tsx

Oops! Something went wrong! :(

ESLint: 9.29.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@typescript-eslint/parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 05e6eda and fd7f48b.

📒 Files selected for processing (3)
  • packages/types/src/supabase.ts (14 hunks)
  • packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx (3 hunks)
  • packages/ui/src/hooks/use-calendar-sync.tsx (7 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx (1)
packages/ui/src/hooks/use-calendar-sync.tsx (1)
  • useCalendarSync (906-913)
🪛 GitHub Check: codecov/patch
packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx

[warning] 15-15: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L15
Added line #L15 was not covered by tests


[warning] 18-18: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L18
Added line #L18 was not covered by tests


[warning] 21-21: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L21
Added line #L21 was not covered by tests


[warning] 87-87: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L87
Added line #L87 was not covered by tests


[warning] 89-89: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L89
Added line #L89 was not covered by tests


[warning] 91-104: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L91-L104
Added lines #L91 - L104 were not covered by tests


[warning] 432-439: packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx#L432-L439
Added lines #L432 - L439 were not covered by tests

packages/ui/src/hooks/use-calendar-sync.tsx

[warning] 69-70: packages/ui/src/hooks/use-calendar-sync.tsx#L69-L70
Added lines #L69 - L70 were not covered by tests


[warning] 129-129: packages/ui/src/hooks/use-calendar-sync.tsx#L129
Added line #L129 was not covered by tests


[warning] 344-347: packages/ui/src/hooks/use-calendar-sync.tsx#L344-L347
Added lines #L344 - L347 were not covered by tests


[warning] 603-603: packages/ui/src/hooks/use-calendar-sync.tsx#L603
Added line #L603 was not covered by tests


[warning] 628-628: packages/ui/src/hooks/use-calendar-sync.tsx#L628
Added line #L628 was not covered by tests


[warning] 630-632: packages/ui/src/hooks/use-calendar-sync.tsx#L630-L632
Added lines #L630 - L632 were not covered by tests


[warning] 635-647: packages/ui/src/hooks/use-calendar-sync.tsx#L635-L647
Added lines #L635 - L647 were not covered by tests


[warning] 884-885: packages/ui/src/hooks/use-calendar-sync.tsx#L884-L885
Added lines #L884 - L885 were not covered by tests

⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Deploy-Preview
  • GitHub Check: Verify generated types
  • GitHub Check: Deploy-Preview
  • GitHub Check: Deploy-Preview
  • GitHub Check: Deploy-Preview
  • GitHub Check: Deploy-Preview
🔇 Additional comments (10)
packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx (3)

15-15: LGTM: Import additions are correct.

The new imports for useCalendarSync, Switch, and useEffect are properly added and necessary for the toggle functionality.

Also applies to: 18-18, 21-21


87-87: LGTM: Proper usage of the calendar sync hook.

The destructuring of setIsActiveSyncOn and isActiveSyncOn from useCalendarSync follows the expected pattern and provides the necessary state management for the toggle.


432-440: LGTM: Clean conditional rendering of the Active Sync toggle.

The toggle is properly wrapped in the conditional check and uses the correct state binding. The UI implementation is clean and follows the expected pattern for controlled components.

packages/ui/src/hooks/use-calendar-sync.tsx (7)

45-45: LGTM: Proper context type extension.

The isActiveSyncOn boolean and setIsActiveSyncOn setter are correctly added to the context type definition with appropriate TypeScript typing.

Also applies to: 49-49


69-70: LGTM: Consistent default context values.

The default values for isActiveSyncOn: false and setIsActiveSyncOn: () => {} are appropriate and consistent with the context pattern used throughout the file.


129-129: LGTM: Standard state initialization.

The isActiveSyncOn state is properly initialized with a default value of false, which is the expected behavior for a toggle that should be opt-in.


344-347: LGTM: Effective guard clause implementation.

The early return when isActiveSyncOn is false provides a clean way to prevent synchronization operations when the toggle is disabled. The console log helps with debugging the sync behavior.


628-647: LGTM: Well-implemented toggle-triggered sync logic.

The new useEffect properly triggers synchronization when:

  1. The toggle is enabled (isActiveSyncOn becomes true)
  2. Google Calendar is connected (workspace ID matches)
  3. Google data is available and not empty

The dependency array is comprehensive and includes all necessary values.


603-603: LGTM: Proper dependency array update.

Adding isActiveSyncOn to the dependency array of the syncToTuturuuu callback ensures the function captures the current state of the toggle.


884-885: LGTM: Complete context value exposure.

The isActiveSyncOn state and setIsActiveSyncOn setter are properly included in the context value, making them available to consuming components.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch feat/toggle-active-sync

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

graphite-app bot commented Jun 19, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@DennieDan DennieDan self-assigned this Jun 19, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @DennieDan, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new 'Active Sync' feature, providing a toggle to control calendar synchronization behavior. This functionality is primarily aimed at facilitating testing of background sync mechanisms by allowing internal users to enable or disable active syncing. The changes include UI additions, a new React hook for state management, and updates to auto-generated database type definitions.

Highlights

  • Active Sync Toggle: Introduced a new UI toggle for 'Active Sync' within the Google Calendar settings, allowing for manual control over the calendar synchronization process.
  • Conditional UI Visibility: The 'Active Sync' toggle is conditionally displayed only to users with @tuturuuu.com email addresses, indicating it's intended for internal testing or specific user groups.
  • Calendar Synchronization Control: Implemented logic within the useCalendarSync hook to block the syncToTuturuuu function (which handles syncing calendar data to the application's database) when 'Active Sync' is disabled.
  • Supabase Type Definition Updates: Updated the auto-generated Supabase type definitions (supabase.ts), primarily involving reordering of properties within function argument and return types, and some property relocations (e.g., created_at moved between user functions, id and display_name moved between search functions). These changes are likely a side effect of schema updates or a type generation process.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

codecov bot commented Jun 19, 2025

Codecov Report

Attention: Patch coverage is 0% with 54 lines in your changes missing coverage. Please review.

Project coverage is 0.80%. Comparing base (05e6eda) to head (fd7f48b).
Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
...acy/calendar/settings/google-calendar-settings.tsx 0.00% 27 Missing ⚠️
packages/ui/src/hooks/use-calendar-sync.tsx 0.00% 27 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3122      +/-   ##
==========================================
- Coverage    0.80%    0.80%   -0.01%     
==========================================
  Files        2542     2542              
  Lines      323788   323840      +52     
  Branches     3043     3043              
==========================================
  Hits         2621     2621              
- Misses     318998   319050      +52     
  Partials     2169     2169              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR introduces a UI toggle to enable/disable "Active Sync" for Google Calendar, primarily for testing background sync functionality. The core changes in the React components and hooks correctly implement this toggle.

The review identified two main points:

  1. Numerous type property reorderings in packages/types/src/supabase.ts seem unrelated to the PR's purpose and add noise to the diff. It's recommended to clarify their origin or consider moving them to a separate PR if they are part of a broader formatting update.
  2. The conditional display of the new toggle in packages/ui/src/components/ui/legacy/calendar/settings/google-calendar-settings.tsx is based on a hardcoded email domain check (@tuturuuu.com). While suitable for a temporary testing feature, a more robust solution (like feature flags or user roles) should be considered if this functionality becomes permanent or needs to be extended.

Overall, the primary goal of the PR is achieved. Addressing the unrelated changes and considering future improvements for the conditional logic would enhance maintainability.

@DennieDan DennieDan marked this pull request as ready for review June 19, 2025 04:02
@DennieDan DennieDan requested a review from vhpx June 19, 2025 07:15
Copy link
Member

@vhpx vhpx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @DennieDan.

@vhpx vhpx merged commit 8e455fa into main Jun 19, 2025
19 checks passed
@vhpx vhpx deleted the feat/toggle-active-sync branch June 19, 2025 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants