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
Currently, we always use the languageDictionary.title entry for the first screen loaded (which can be changed with the initialScreen option). So, even though you set languageDictionary.forgotPasswordTitle, if you set initialScreen: forgotPassword, it will use languageDictionary.title as the string and not languageDictionary.forgotPasswordTitle. This becomes a particular hard issue to handle if you're trying to use Lock's internal i18n dictionary, since you'd have to override forgotPasswordTitle based on which language you're trying to load Lock with.
After some discussion, we agreed to have the behavior changed to:
Assuming we're in the forgot password screen, for example:
If you have a screen specific title (languageDictionary.forgotPassswordTitle), use that
Else use Lock's default dictionary entry for that screen
The text was updated successfully, but these errors were encountered:
Currently, we always use the
languageDictionary.title
entry for the first screen loaded (which can be changed with theinitialScreen
option). So, even though you setlanguageDictionary.forgotPasswordTitle
, if you setinitialScreen: forgotPassword
, it will uselanguageDictionary.title
as the string and notlanguageDictionary.forgotPasswordTitle
. This becomes a particular hard issue to handle if you're trying to use Lock's internal i18n dictionary, since you'd have to overrideforgotPasswordTitle
based on which language you're trying to load Lock with.After some discussion, we agreed to have the behavior changed to:
Assuming we're in the forgot password screen, for example:
languageDictionary.forgotPassswordTitle
), use thatThe text was updated successfully, but these errors were encountered: