-
Notifications
You must be signed in to change notification settings - Fork 240
fix: add missing space symbol to the 'additional.help.text' field #1521
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
base: master
Are you sure you want to change the base?
fix: add missing space symbol to the 'additional.help.text' field #1521
Conversation
|
Thanks for the pull request, @bydawen! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. Where can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1521 +/- ##
=======================================
Coverage 87.57% 87.57%
=======================================
Files 125 125
Lines 2309 2309
Branches 644 648 +4
=======================================
Hits 2022 2022
Misses 278 278
Partials 9 9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| </Hyperlink> | ||
| )} | ||
| <p className="mt-5.5 small text-gray-700"> | ||
| {formatMessage(messages['additional.help.text'], { platformName })} |
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.
[nit] Please also remove a whitespace in the end of the translation
https://github.com/raccoongang/frontend-app-authn/blob/03af30e8df93caf926f22eb6c0768a215fe07c8f/src/forgot-password/messages.js#L77
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.
[nit] Please also remove a whitespace in the end of the translation https://github.com/raccoongang/frontend-app-authn/blob/03af30e8df93caf926f22eb6c0768a215fe07c8f/src/forgot-password/messages.js#L77
removed, thx!
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.
It looks like this is exactly the issue that this PR is meant to address. Right now, the translation file includes a space between the text For additional help, contact {platformName} support at and the <span> element with the link. While this technically works, and we do see a visible space - it’s not a reliable or correct approach.
It also leads to inconsistencies: in some translations the space may be missing entirely, because it’s not intuitive for translators to include it at the end of a string. That’s why this behavior ends up breaking in certain languages.
668e7fd to
6b9e407
Compare
sundasnoreen12
left a comment
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.
Hi @bydawen, Kindly rebase this PR
6b9e407 to
0466364
Compare
Hello, done) |
|
kindly rebase this PR, @bydawen |
0466364 to
5cf1541
Compare
Hi, done! |
6b035f3 to
2f6e97e
Compare
2f6e97e to
854904d
Compare
854904d to
3505e16
Compare
|
Hi @bydawen @sundasnoreen12 @ihor-romaniuk @awais-ansari is this still in progress? |
PKulkoRaccoonGang
left a comment
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.
Thanks for the PR! I left a few comments that, in my opinion, clarify the root cause of the issue and outline a potential technical solution that should allow us to land this PR.
| </Hyperlink> | ||
| )} | ||
| <p className="mt-5.5 small text-gray-700"> | ||
| {formatMessage(messages['additional.help.text'], { platformName })} |
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.
It looks like this is exactly the issue that this PR is meant to address. Right now, the translation file includes a space between the text For additional help, contact {platformName} support at and the <span> element with the link. While this technically works, and we do see a visible space - it’s not a reliable or correct approach.
It also leads to inconsistencies: in some translations the space may be missing entirely, because it’s not intuitive for translators to include it at the end of a string. That’s why this behavior ends up breaking in certain languages.
| | ||
| <span> |
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.
Given my earlier comment about the root cause of the spacing issue, I don’t think adding a non-breaking space ( ) is the right long-term solution. Spacing between HTML elements should ideally be handled by CSS whenever possible.
So instead, I’d suggest shifting this responsibility to a Paragon CSS utility class mx-1 which will reliably provide horizontal spacing and will work correctly for both LTR and RTL layouts.
| | |
| <span> | |
| <span class="mx-1"> |
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.
Given my earlier comment about the root cause of the spacing issue, I don’t think adding a non-breaking space (
) is the right long-term solution. Spacing between HTML elements should ideally be handled by CSS whenever possible.So instead, I’d suggest shifting this responsibility to a Paragon CSS utility class
mx-1which will reliably provide horizontal spacing and will work correctly for both LTR and RTL layouts.
fixed, thx!
|
Sandbox deployment failed 💥 |
|
Sandbox deployment successful 🚀 |
3505e16 to
4e9a7c4
Compare
4e9a7c4 to
2ba9753
Compare
|
Sandbox deployment failed 💥 |
PKulkoRaccoonGang
left a comment
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!
|
Sandbox deployment successful 🚀 |
|
Sandbox deployment successful 🚀 |
There is a issue, that almost in all translations there is no space between
"additional.help.text"field and{getConfig().INFO_EMAIL}in the frontend-app-authnTo prevent this, and not to fix all translations files, space symbol was added.