You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
storage-wrapper methods to be sync when not running on E2E mode
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
joaoloureirop
changed the title
refactor: make storage wrapper operations synchronous
refactor: make storage-wrapper operations synchronous
Jan 9, 2025
What is this about?
Now that we use MMKV, device storage operations are synchronous.
Our storage-wrapper methods are async only to support E2E, causing the whole storage-wrapper class to be behind a promise based architecture.
We need to decouple E2E fallbacks from the storage-wrapper implementation to have properly typed mmkv operations.
Scenario
N/A
Design
N/A
Technical Details
PR feat: Enable feature Flag Values with Scope Based on "threshold" in mobile has a draft commit on how it expects storage-wrapper interface to be.
Threat Modeling Framework
N/A
Acceptance Criteria
storage-wrapper methods to be sync when not running on E2E mode
Stakeholder review needed before the work gets merged
References
Epic: #10784
The text was updated successfully, but these errors were encountered: