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

chore(IT Wallet): [SIW-1949] Display email address in the same line in issuance failure screen #6589

Merged
merged 2 commits into from
Jan 9, 2025

Conversation

gispada
Copy link
Collaborator

@gispada gispada commented Jan 8, 2025

Short description

This PR changes the line break strategy in the issuance failure screens to display email addresses in the same line. The issue seems to affect Android devices only.

List of changes proposed in this pull request

  • Added textBreakStrategy: "simple" in ItwIssuanceEidFailureScreen and ItwIssuanceCredentialFailureScreen

How to test

The easiest way to test it is to mock an error during credential issuance with a message that contains an email address.

Before After

@gispada gispada requested review from ChrisMattew, freddi301 and a team as code owners January 8, 2025 09:24
Copy link
Contributor

github-actions bot commented Jan 8, 2025

Jira Pull Request Link

This Pull Request refers to the following Jira issue SIW-1949

Copy link

codecov bot commented Jan 8, 2025

Codecov Report

Attention: Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.

Project coverage is 49.28%. Comparing base (ecd87bc) to head (99cdc98).
Report is 8 commits behind head on master.

Files with missing lines Patch % Lines
...nce/screens/ItwIssuanceCredentialFailureScreen.tsx 0.00% 1 Missing ⚠️
...t/issuance/screens/ItwIssuanceEidFailureScreen.tsx 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #6589   +/-   ##
=======================================
  Coverage   49.28%   49.28%           
=======================================
  Files        1558     1558           
  Lines       32156    32156           
  Branches     7325     7326    +1     
=======================================
  Hits        15849    15849           
  Misses      16258    16258           
  Partials       49       49           
Files with missing lines Coverage Δ
...omponents/screens/OperationResultScreenContent.tsx 100.00% <100.00%> (ø)
...nce/screens/ItwIssuanceCredentialFailureScreen.tsx 9.25% <0.00%> (ø)
...t/issuance/screens/ItwIssuanceEidFailureScreen.tsx 6.97% <0.00%> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ed401c...99cdc98. Read the comment docs.

@gispada gispada added this pull request to the merge queue Jan 9, 2025
Merged via the queue into master with commit 22ca3e6 Jan 9, 2025
23 checks passed
@gispada gispada deleted the SIW-1949-issuance-failure-line-break branch January 9, 2025 07:27
LazyAfternoons pushed a commit that referenced this pull request Jan 9, 2025
…n issuance failure screen (#6589)

## Short description
This PR changes the line break strategy in the issuance failure screens
to display email addresses in the same line. The issue seems to affect
Android devices only.

## List of changes proposed in this pull request
- Added `textBreakStrategy: "simple"` in `ItwIssuanceEidFailureScreen`
and `ItwIssuanceCredentialFailureScreen`

## How to test
The easiest way to test it is to mock an error during credential
issuance with a message that contains an email address.

|Before|After|
|------|-----|
|<img
src="https://github.com/user-attachments/assets/fe546b8e-249a-4955-921f-39106dfa1242"
width="240"/>|<img
src="https://github.com/user-attachments/assets/ad478750-93a5-4b5c-8024-2d166c4be92d"
width="240"/>|
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