Skip to content
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

Import progress for room keys #7078

Merged
merged 1 commit into from
Nov 15, 2022
Merged

Import progress for room keys #7078

merged 1 commit into from
Nov 15, 2022

Conversation

Anderas
Copy link
Contributor

@Anderas Anderas commented Nov 15, 2022

SDK change

If we are actively importing keys from backup, display the current import progress as a percentage in the settings, whilst disabling the "restore from backup" button. The import progress replaces the previously unused backup progress.

To keep the progress updating I had to add a simple 1s timer, though I don't think this works very well with the current view model architecture, as it forces the entire section to refresh, leading to visible refresh of the other button rows. In practice only the WIP Crypto V2 will trigger this behaviour, because legacy crypto always returns nil for import progress. This means we can improve the UI behaviour in a future PR

In progress Done
Simulator Screen Shot - iPhone 14 Pro - 2022-11-15 at 12 01 49 Simulator Screen Shot - iPhone 14 Pro - 2022-11-15 at 12 06 46

@sonarcloud
Copy link

sonarcloud bot commented Nov 15, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@Anderas Anderas requested review from a team and stefanceriu and removed request for a team November 15, 2022 12:09
Copy link
Member

@stefanceriu stefanceriu left a comment

Choose a reason for hiding this comment

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

lgtm 👍

@codecov
Copy link

codecov bot commented Nov 15, 2022

Codecov Report

Base: 11.66% // Head: 11.74% // Increases project coverage by +0.08% 🎉

Coverage data is based on head (20668a5) compared to base (602cf76).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #7078      +/-   ##
===========================================
+ Coverage    11.66%   11.74%   +0.08%     
===========================================
  Files         1620     1620              
  Lines       158997   158900      -97     
  Branches     64678    64611      -67     
===========================================
+ Hits         18540    18669     +129     
+ Misses      139816   139594     -222     
+ Partials       641      637       -4     
Flag Coverage Δ
uitests 54.89% <ø> (+0.29%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...eBackup/SettingsSecureBackupTableViewSection.swift 0.00% <0.00%> (ø)
...y/SecureBackup/SettingsSecureBackupViewModel.swift 0.00% <0.00%> (ø)
...Modules/Settings/Security/SecurityViewController.m 0.00% <ø> (ø)
RiotSwiftUI/Modules/Common/Mock/ScreenList.swift 84.31% <0.00%> (-5.89%) ⬇️
...UserSessions/Common/View/UserSessionCardView.swift 50.75% <0.00%> (+1.09%) ⬆️
...rOtherSessions/View/UserOtherSessionsToolbar.swift 89.61% <0.00%> (+1.29%) ⬆️
...Sessions/Common/View/UserSessionCardViewData.swift 88.15% <0.00%> (+1.31%) ⬆️
...serSessionsOverview/View/UserSessionListItem.swift 64.28% <0.00%> (+2.92%) ⬆️
... and 15 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

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