fix(settings): missing 3rd-party auth string#19441
Conversation
|
|
||
| # For the sign-in page, when 3rd-party auth is the only option, this string appears with a divider line between the user's avatar on top and 3rd-party authentication buttons (continue-with-google continue-with-apple buttons) on bottom. | ||
| # This could also be translated as "Sign in with the following" or "Sign in with the below". | ||
| third-party-auth-options-sign-in-with = Sign in with |
There was a problem hiding this comment.
I might be missing something but where is the fall back text for this? If we want to go with it just being "or", I'd just call out this is the only place where we'd rely on Fluent to replace the text for us 🤔
There was a problem hiding this comment.
@LZoog It defaults to "or" here:
– is there a better place to hold the default, or would you like me to add context about the default in the l10n comment?There was a problem hiding this comment.
It doesn't matter to translators, more of an us thing so if Fluent doesn't replace the text or the ID is missing or any other reason, the correct English string would display. It would be my preference that "or" is used as the default for the corresponding FTL ID, and "Sign in with" has its own <FtlMsg> wrapper. I think this would need some tweaking so they've got their own FtlMsg:
<FtlMsg id={separatorTextId || 'third-party-auth-options-or'}>
<div className="mx-4 text-base text-grey-300 font-extralight">
or
</div>
</FtlMsg>
There was a problem hiding this comment.
This can be done in another PR if you want btw, I know this one's just to add the string back, I'll r+ to unblock Bryan in case he's trying to get these over to Pontoon.
There was a problem hiding this comment.
The better way is to pass in the localized string directly instead of passing in the FTL id, so that you can pass in ftlMessageResolver.getMsg('custom-ftl-id', 'Customized string') and get the customized fallback.
There was a problem hiding this comment.
Yep, that works too and agreed is preferable in this case!
There was a problem hiding this comment.
will merge this for translation and improve under separate PR 👍
Because
This pull request