Skip to content

Conversation

@bydawen
Copy link
Contributor

@bydawen bydawen commented Jul 14, 2025

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-authn

wqa122a

To prevent this, and not to fix all translations files, space symbol was added.

@bydawen bydawen requested a review from a team as a code owner July 14, 2025 10:46
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Jul 14, 2025
@openedx-webhooks
Copy link

Thanks for the pull request, @bydawen!

This repository is currently maintained by @openedx/2u-infinity.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To 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:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If 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:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation bot moved this to Needs Triage in Contributions Jul 14, 2025
@bydawen bydawen self-assigned this Jul 14, 2025
@codecov
Copy link

codecov bot commented Jul 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.57%. Comparing base (882545b) to head (2ba9753).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mphilbrick211 mphilbrick211 moved this from Needs Triage to Ready for Review in Contributions Jul 15, 2025
</Hyperlink>
)}
<p className="mt-5.5 small text-gray-700">
{formatMessage(messages['additional.help.text'], { platformName })}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 668e7fd to 6b9e407 Compare July 21, 2025 15:10
Copy link
Contributor

@sundasnoreen12 sundasnoreen12 left a 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

@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 6b9e407 to 0466364 Compare August 7, 2025 11:31
@bydawen
Copy link
Contributor Author

bydawen commented Aug 7, 2025

Hi @bydawen, Kindly rebase this PR

Hello, done)

@sundasnoreen12
Copy link
Contributor

kindly rebase this PR, @bydawen

@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 0466364 to 5cf1541 Compare August 12, 2025 06:23
@bydawen
Copy link
Contributor Author

bydawen commented Aug 12, 2025

kindly rebase this PR, @bydawen

Hi, done!

@ihor-romaniuk ihor-romaniuk force-pushed the fix/missing-space-in-forgot-password-field branch 2 times, most recently from 6b035f3 to 2f6e97e Compare August 28, 2025 12:23
@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 2f6e97e to 854904d Compare September 11, 2025 09:38
@mphilbrick211 mphilbrick211 moved this from Ready for Review to In Eng Review in Contributions Sep 16, 2025
@mphilbrick211 mphilbrick211 added the waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc. label Sep 24, 2025
@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 854904d to 3505e16 Compare October 15, 2025 10:19
@mphilbrick211 mphilbrick211 removed the waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc. label Oct 29, 2025
@mphilbrick211 mphilbrick211 moved this from In Eng Review to Ready for Review in Contributions Oct 29, 2025
@mphilbrick211
Copy link

Hi @bydawen @sundasnoreen12 @ihor-romaniuk @awais-ansari is this still in progress?

@PKulkoRaccoonGang PKulkoRaccoonGang added the create-sandbox open-craft-grove should create a sandbox environment from this PR label Nov 16, 2025
Copy link

@PKulkoRaccoonGang PKulkoRaccoonGang left a 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 })}

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.

Comment on lines 156 to 157
&nbsp;
<span>

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 (&nbsp;) 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.

Suggested change
&nbsp;
<span>
<span class="mx-1">

Copy link
Contributor Author

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 (&nbsp;) 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.

fixed, thx!

@open-craft-grove
Copy link

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

@open-craft-grove
Copy link

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 3505e16 to 4e9a7c4 Compare November 26, 2025 09:30
@bydawen bydawen force-pushed the fix/missing-space-in-forgot-password-field branch from 4e9a7c4 to 2ba9753 Compare November 26, 2025 09:33
@open-craft-grove
Copy link

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

Copy link

@PKulkoRaccoonGang PKulkoRaccoonGang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@open-craft-grove
Copy link

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

@open-craft-grove
Copy link

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

@mphilbrick211 mphilbrick211 moved this from Ready for Review to In Eng Review in Contributions Dec 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

create-sandbox open-craft-grove should create a sandbox environment from this PR open-source-contribution PR author is not from Axim or 2U

Projects

Status: In Eng Review

Development

Successfully merging this pull request may close these issues.

8 participants