You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user signs up with a social account but the project settings require additional identifier (e.g. username, phone number ect.) or additional information (e.g. Full Name), a screen should be shown to the user to collect the additional required data.
Create a MissingFields screen according to the Figma Draft "S1.7.1 MissingFields". The screen can contain one or more fields of identifier and the data is provided by the FAPI.
Design the screen according to the Figma drafts but keep the style as much similar as possible to the initSignup screen (Fonts, Paddings ect.)
When clicking on the "Continue" button, a API call should be made to the BE to validate the input data. If errors occur, show them in the same style as in the signupInit screen.
Acceptance criteria
MissingFields screen is shown if additional identifier are required than provided by the social account.
Enterd identifier are validated and errors are correctly provided to the FE
Signup with social logins continues to work as usual.
Implementation idea
Here you can write down an implementation idea how you would implement this issue (where do put this feature like in what domain, what service, what layer, naming/key of the feature in the code).
The text was updated successfully, but these errors were encountered:
Adam3371
changed the title
Add a MissinField screen to the missing-identifier-collect block.
Add a MissingField screen to the missing-identifier-collect block.
Jun 12, 2024
Why
This is a follow up ticket to the "Add Missing-Identifier-collect block" Ticket and can only be started, once the Prio 1 tasks are completed.
If a user signs up with a social account but the project settings require additional identifier (e.g. username, phone number ect.) or additional information (e.g. Full Name), a screen should be shown to the user to collect the additional required data.
Figma Draft
TODOS
Acceptance criteria
Implementation idea
Here you can write down an implementation idea how you would implement this issue (where do put this feature like in what domain, what service, what layer, naming/key of the feature in the code).
The text was updated successfully, but these errors were encountered: