-
Notifications
You must be signed in to change notification settings - Fork 907
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
[Auth] Fix error typing and bring MFA error into alignment with the current API standard #5616
Conversation
* fix interface AuthError change interface AuthError to correct structure * remove `declare`
🦋 Changeset detectedLatest commit: b4ae127 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Binary Size ReportAffected SDKs
Test Logs
|
Size Analysis ReportAffected Products
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a couple nits
Comment in English is not my advantage, I prefer the new comments. |
Co-authored-by: Kevin Cheung <kevinthecheung@users.noreply.github.com>
@sam-gc Thank for fixting this! I think this closes #5599. Please confirm.
|
Specifically,
MultiFactorError
was putting fields on the error itself instead oferror.customData
. The mainAuthError
was doing the right thing in the code, but the public typing was wrong. With this PR both the typing and the implementation should be consistent using the new API standard (by putting everything onerror.customData
). Thanks @Pablion for catching the issue. The reference docs will update automatically with this PR.