generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 15
Closed
Labels
authenticatorThis issue relates to the Authenticator componentThis issue relates to the Authenticator componentfeature-requestNew feature or requestNew feature or request
Description
Before opening, please confirm:
Which UI component is this feature-request for?
Authenticator
Please include any relevant guides or documentation you're referencing
No response
Please describe your feature-request in detail.
On the Swift Authenticator, you can specify string content for any cognito error by using a specific string key, even if Authenticator itself doesn't have any logic for that case. We should implement a similar system on Android.
- When resolving the string content for an error scenario, first check to see if application has defined a specific string for that exception.
- If not, use the default string specified in Authenticator.
The list of exceptions we can expect to receive can be found here. We can transform the exception type into a string resource ID using some known algorithm, something like:
- Strip the "Exception" suffix
- Transform the remaining name to snake_case
- Prepend
amplify_ui_authenticator_error_
This would result in e.g. ParseTokenException
resolving to a string R.string.amplify_ui_authenticator_error_parse_token
that could be defined in the application resources to set the content for this exception.
Initialization steps (if applicable)
No response
Code Snippet
// Put your code below this line.
amplifyconfiguration.json
No response
Additional information and screenshots
No response
Metadata
Metadata
Assignees
Labels
authenticatorThis issue relates to the Authenticator componentThis issue relates to the Authenticator componentfeature-requestNew feature or requestNew feature or request