-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[Translation] Prevent creating empty keys when key ends with a period #52005
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
Merged
nicolas-grekas
merged 1 commit into
symfony:5.4
from
javleds:ticket_51536_fix_empty_yam_tranlation_keys
Oct 13, 2023
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think we can simplify this method with something like:
Uh oh!
There was an error while loading. Please reload this page.
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 @welcoMattic. I love short code...
Nevertheless the shared code has 2 small disadvantages:
Please see the test of this section for more info.
If I am not addressing something, please let me know, I will be glad to adjust the PR if needed.
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.
for php version, you can leverage symfony/polyfill-php (find the one v that introduced the relevant function)
Uh oh!
There was an error while loading. Please reload this page.
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.
The polyfill that introduces
str_starts_with
andstr_ends_with
is symfony/polyfill-php80, and it is already required in the Translation component so using those functions is ok imoThere 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.
ho indeed cool if already included
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.
@javleds It seems the edge cases you mention are covered by simplier code here:
https://3v4l.org/2ic9k
Uh oh!
There was an error while loading. Please reload this page.
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.
Getting back to the code discussion:
The real problem here is to avoid trimming the periods at the beginning/end of the parts. Since the
getElementByPath
function is itended to process each part as a valid string. Having empty positions or a position wihtn a single dot won't give the expected result.For example:
['foo', 'bar']
will give the expected result.['foo', '', 'bar']
won't give the expected result due the empty position.['foo', 'bar', '.']
won't give the expected result due the period at position 2.['.foo', 'bar.']
will give the expected result.The simpler solution is to keep the period concatenated to the key part, and prevent the period occupate a single possition in the array. Otherwise, we will have to add extra processing inside the
getElementByPath
function.Having this in mind, the code proposed above has small variations on the expected result.
Let me give the examples:
If the proposed solution is hard to read, maybe, we can create named variables for every
if
statement.