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

feat(Firma con IO): [SFEQS-2083] Replace abort bottom sheet with alert #5425

Merged
merged 16 commits into from
Feb 23, 2024

Conversation

LazyAfternoons
Copy link
Contributor

@LazyAfternoons LazyAfternoons commented Jan 23, 2024

Short description

This PR replaces the abort bottom sheet with an alert when using the new design system, according to this FIGMA.
The shown alert is just a placeholder for a nativa alert, thus we are leaving Apple and OEMs for Android to decide how it looks on each device, including the order of the buttons.
On iOS the style: 'cancel' prop places the button as second when text requires wrapping. On Android, two buttons means negative, positive and are placed accordingly (ref).

List of changes proposed in this pull request

  • Add locales;
  • Override the present function of the bottom sheet to show an alert instead if the experimental design is enabled.
    This allows us to use an alert without changing single components which use the hook.
    The bottom sheet will be removed once the experimental design is enabled by default (SFEQS-2090).

How to test

Open a signature flow either in production or with io-dev-api-server by setting the flag waitForSignatureCount: 1. Then try to abort it. Either a bottom sheet or an alert should be displayed if the experimental design system is disabled or not.

@pagopa-github-bot pagopa-github-bot changed the title [SFEQS-2083] Replace abort bottom sheet with alert feat(Firma con IO): [SFEQS-2083] Replace abort bottom sheet with alert Jan 23, 2024
@pagopa-github-bot
Copy link
Collaborator

pagopa-github-bot commented Jan 23, 2024

Affected stories

  • 🌟 SFEQS-2083: Sostituire le bottom sheet di annullamento del flusso con una dialog
    subtask of

Generated by 🚫 dangerJS against 718b6dd

@LazyAfternoons LazyAfternoons marked this pull request as ready for review January 23, 2024 10:58
@LazyAfternoons LazyAfternoons requested review from thisisjp and a team as code owners January 23, 2024 10:58
Copy link

codecov bot commented Jan 23, 2024

Codecov Report

Attention: Patch coverage is 50.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 47.83%. Comparing base (106c7df) to head (718b6dd).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #5425   +/-   ##
=======================================
  Coverage   47.82%   47.83%           
=======================================
  Files        1418     1418           
  Lines       30704    30710    +6     
  Branches     7467     7467           
=======================================
+ Hits        14685    14689    +4     
- Misses      15960    15962    +2     
  Partials       59       59           
Files Coverage Δ
ts/features/fci/hooks/useFciAbortSignatureFlow.tsx 65.00% <50.00%> (+0.71%) ⬆️

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 106c7df...718b6dd. Read the comment docs.

Copy link
Contributor

@hevelius hevelius left a comment

Choose a reason for hiding this comment

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

LGTM

@LazyAfternoons LazyAfternoons force-pushed the SFEQS-2083-replace-dialog branch from e81edac to 2fc1faf Compare February 23, 2024 14:34
@LazyAfternoons LazyAfternoons merged commit 9d33b39 into master Feb 23, 2024
8 checks passed
@LazyAfternoons LazyAfternoons deleted the SFEQS-2083-replace-dialog branch February 23, 2024 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants