feat(authenticator): Allow customer to override error strings per exception type #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: #181
Description of changes:
Customer can set the error content for a particular AuthException by setting a string like e.g.
amplify_ui_authenticator_error_invalid_state
to provide content forInvalidStateException
This applies to the
AuthenticatorError
content and toUnknownError
snackbar messages. Other types of errors (field level errors, other snackbar messages) have specific strings that can already be replaced.How did you test these changes?
Documentation update required?
General Checklist
fix(liveness): message
,fix(authenticator): message
,fix(all): message
)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.