Skip to content

feat : Feature flag cross device sync#1064

Open
sricharan-varanasi wants to merge 15 commits intoM2-10227-local-vs-server-syncfrom
feature-flag-cross-device-sync
Open

feat : Feature flag cross device sync#1064
sricharan-varanasi wants to merge 15 commits intoM2-10227-local-vs-server-syncfrom
feature-flag-cross-device-sync

Conversation

@sricharan-varanasi
Copy link
Copy Markdown
Contributor

  • Tests for the changes have been added
  • Related documentation has been added / updated
  • OSS packages added to Curious open source credit page

📝 Description

Adds feature flag gating for cross-device flow sync functionality to allow safe rollout.

Changes include:

  • Add enable-cross-device-flow-sync feature flag (default: OFF)
  • Gate all cross-device sync behavior behind the flag
  • When flag is OFF, app behaves exactly like dev branch
  • When flag is ON, enables syncing in-progress flows across devices

✏️ Notes

  • This PR gates all 38 files changed in M2-10227-local-vs-server-sync
  • No behavioral changes when flag is OFF
  • Related to web PR for cross-device flow sync

@sricharan-varanasi sricharan-varanasi changed the base branch from M2-10227-local-vs-server-sync to dev February 10, 2026 22:38
@sricharan-varanasi sricharan-varanasi force-pushed the feature-flag-cross-device-sync branch from 92764b7 to ed539a6 Compare February 10, 2026 22:46
@sricharan-varanasi sricharan-varanasi changed the base branch from dev to M2-10227-local-vs-server-sync February 10, 2026 23:30
@sricharan-varanasi sricharan-varanasi force-pushed the feature-flag-cross-device-sync branch 3 times, most recently from d04cd4e to 4424b61 Compare February 11, 2026 18:36
@sricharan-varanasi sricharan-varanasi force-pushed the feature-flag-cross-device-sync branch from 4424b61 to 4ef0e94 Compare February 13, 2026 21:50
Copy link
Copy Markdown
Contributor

@divbzero divbzero left a comment

Choose a reason for hiding this comment

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

Overall looks good! Just one suggestion for a minor change.

Comment on lines +65 to +66
startTime?: number; // millisecond timestamp when activity/flow started
endTime?: number; // millisecond timestamp when activity/flow ended
Copy link
Copy Markdown
Contributor

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 need to make startTime and endTime into optional startTime? and endTime?. Those values are not nullable on the backend:

    start_time: datetime.datetime
    end_time: datetime.datetime

https://github.com/ChildMindInstitute/mindlogger-backend-refactor/blob/2026.01.3/src/apps/answers/domain/answers.py#L679-L680

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