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
As reported in #3723, the API of Realm.Auth.EmailPasswordAuth.resetPassword() is not consistent between Realm Web and Realm JavaScript. Moreover, the TypeScript definition says on thing, and the API documentation says something else. The root cause is positional arguments (all strings) which is error prone for both our users and for ourself.
We should deprecate all current methods of Realm.Auth.EmailPasswordAuth (to be removed in version 11) and implement a new variant of the API:
callResetPasswordFunction({email: string,password: string},args: [BSON])confirmUser({token: string,id: string})registerUser({email: string,password: string})resendConfirmationEmail({email: string})// for consistencyresetPassword({password: string,token: string,id: string})sendResetPasswordEmail({email: string})// for consistency
Methods should log a warning if called with deprecated signature.
The text was updated successfully, but these errors were encountered:
As reported in #3723, the API of
Realm.Auth.EmailPasswordAuth.resetPassword()
is not consistent between Realm Web and Realm JavaScript. Moreover, the TypeScript definition says on thing, and the API documentation says something else. The root cause is positional arguments (all strings) which is error prone for both our users and for ourself.We should deprecate all current methods of
Realm.Auth.EmailPasswordAuth
(to be removed in version 11) and implement a new variant of the API:Methods should log a warning if called with deprecated signature.
The text was updated successfully, but these errors were encountered: