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

Recovery key formatting and wording iteration #3409

Merged
merged 3 commits into from
Sep 6, 2024

Conversation

bmarty
Copy link
Member

@bmarty bmarty commented Sep 6, 2024

Content

If a passphrase is entered by the user the RecoveryKeyVisualTransformation does not apply. This PR is adding 2 screenshots to demo this.

Also stop using the wording screen_recovery_key_confirm_key_label (Recovery key or passcode), it was wrong. Just use Recovery key (similar to iOS and compliant with design)

Motivation and context

Improve wording and screenshot test.

Screenshots / GIFs

Tests

  • Observe the new wording and recovery key formatting when its a passphrase in the recorded screenshots.

Tested devices

  • Physical
  • Emulator
  • OS version(s):

Checklist

  • Changes have been tested on an Android device or Android emulator with API 23
  • UI change has been tested on both light and dark themes
  • Accessibility has been taken into account. See https://github.com/element-hq/element-x-android/blob/develop/CONTRIBUTING.md#accessibility
  • Pull request is based on the develop branch
  • Pull request title will be used in the release note, it clearly define what will change for the user
  • Pull request includes screenshots or videos if containing UI changes
  • Pull request includes a sign off
  • You've made a self review of your PR

@bmarty bmarty requested a review from a team as a code owner September 6, 2024 06:45
@bmarty bmarty requested review from jmartinesp and removed request for a team September 6, 2024 06:45
@bmarty bmarty added the PR-Misc For other changes label Sep 6, 2024
Copy link
Member Author

Choose a reason for hiding this comment

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

Not sure why this is recorded again, the timestamp is not rendered the same way :/.
There is no change in this PR about this.

Copy link
Member

Choose a reason for hiding this comment

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

This was recorded from a fork, maybe their CI setup is somehow in a different TZ?

Copy link
Contributor

github-actions bot commented Sep 6, 2024

📱 Scan the QR code below to install the build (arm64 only) for this PR.
QR code
If you can't scan the QR code you can install the build via this link: https://i.diawi.com/5uHPCS

Copy link

sonarcloud bot commented Sep 6, 2024

Copy link
Member

@jmartinesp jmartinesp left a comment

Choose a reason for hiding this comment

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

Thanks!

Copy link

codecov bot commented Sep 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.62%. Comparing base (9f2db3e) to head (bab85c7).
Report is 19 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #3409   +/-   ##
========================================
  Coverage    82.62%   82.62%           
========================================
  Files         1694     1694           
  Lines        39685    39686    +1     
  Branches      4831     4830    -1     
========================================
+ Hits         32788    32789    +1     
  Misses        5205     5205           
  Partials      1692     1692           

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

@bmarty bmarty added the Run-Maestro Starts a Maestro Cloud session to run integration tests label Sep 6, 2024
@github-actions github-actions bot removed the Run-Maestro Starts a Maestro Cloud session to run integration tests label Sep 6, 2024
@bmarty bmarty merged commit 9b791b6 into develop Sep 6, 2024
33 checks passed
@bmarty bmarty deleted the feature/bma/recoveryKeyFormatting branch September 6, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR-Misc For other changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants