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: [IOPID-1507] Integrate new DS in Pin Screen flow #5737
base: master
Are you sure you want to change the base?
Conversation
…rding-app-pin-screen
Affected stories
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5737 +/- ##
==========================================
+ Coverage 48.42% 49.80% +1.38%
==========================================
Files 1488 1629 +141
Lines 31617 32268 +651
Branches 7669 7728 +59
==========================================
+ Hits 15311 16072 +761
+ Misses 16238 16142 -96
+ Partials 68 54 -14
... and 550 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
@mariateresaventura copy review needed 🙏🏼 |
…rding-app-pin-screen
Short description
Split Pin Screen in two dedicated components
List of changes proposed in this pull request
PinCreation
andPinConfirmation
components which respectively handle the pin creation and confirmation workflowsProfile
section with a non-blocking toast message**CodeInput
component with a custom wrapper delegated to trigger keyboard opening on element focusNote
** The need to restart the application after the pin was changed comes from this PR to make it immediately available in app. Today this behavior is not necessary anymore because the pin is now retrieved directly from
react-native-keychain
when needed.Test
E2E
Tip
Screens
iOS
iOS-onboarding-pin-creation.mp4
iOS-change-pin-success.mp4
iOS-pin-validation-error.mp4
iOS-pin-confirmation-error.mp4
Android
Android-onboarding-pin-creation.mp4
Android-change-ping-success.mp4
Android-pin-validation-error.mp4
Android-pin-confirmation-error.mp4
Accessibility iOS & Android
a11y-.MP4
a11y-.mp4
How to test
Since this component is used in two sections of the app -
Onboarding
andProfile
flows - there are two different ways in which it can be tested.Profile section
This is the easiest way in which it can be tested:
Profile > Security > Change the unlock code
Onboarding section
Testing in local environment - clone io-dev-api-server repo if you haven't did it yet and follow the instructions - go in
config/config.json
and inprofile.attrs
add a fiscal code underfiscal_code
key (must be 16 characters long), restart you backend and then restart the application to login again and display the onboarding flow with the new Pin Screen.Tip
To try multiple times repeat the process changing at least one
fiscal_code
character