Skip to content

[BITAU-152] Handle Vault Lock/Unlock with Sync #998

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 92 commits into from
Oct 7, 2024

Conversation

brant-livefront
Copy link
Collaborator

🎟️ Tracking

BITAU-152

📔 Objective

As I mentioned in the previous PR, I needed to add explicit handling of vault lock/unlock status when performing sync. This PR adds subscribers for both the vault status as well as the sync setting. When either is updated (for any account), we examine if that account is ready for sync or not. To be ready for sync, the user must have opted in to sync and they must have an unlocked vault. If either of those are missing, we dismantle any cipher listening and wait for another signal. I've also added a lot of tests to cover all the various scenarios with multiple accounts.

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

…ges out of DataStore to prepare for refactor in the brant/create-coredata-store branch
…M app CoreData semantics. Refactor conveience methods to new service class
Copy link
Contributor

github-actions bot commented Oct 3, 2024

Logo
Checkmarx One – Scan Summary & Details3926ea92-0c43-4d9f-b269-3d2fe0d885c4

No New Or Fixed Issues Found

Copy link

codecov bot commented Oct 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.07%. Comparing base (77ec482) to head (d15186c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #998   +/-   ##
=======================================
  Coverage   89.07%   89.07%           
=======================================
  Files         660      660           
  Lines       41292    41292           
=======================================
+ Hits        36780    36781    +1     
+ Misses       4512     4511    -1     

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

fedemkr
fedemkr previously approved these changes Oct 3, 2024
Copy link
Member

@fedemkr fedemkr left a comment

Choose a reason for hiding this comment

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

Looks good on my side! However I'd wait for @matt-livefront and @KatherineInCode to review as well in case I've missed something.

matt-livefront
matt-livefront previously approved these changes Oct 7, 2024
Copy link
Collaborator

@matt-livefront matt-livefront left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@brant-livefront brant-livefront merged commit 043c1c7 into main Oct 7, 2024
7 checks passed
@brant-livefront brant-livefront deleted the brant/BITAU-152-handle-vault-lock-unlock branch October 7, 2024 16:56
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.

3 participants