Use a unique key for safariButtonAccessibilityLabel
#19651
Merged
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.
While testing the syntax for Automattic/a8c-ci-toolkit-buildkite-plugin#36, I noticed that
ios_generate_strings_file_from_codeontrunk(33e65ab7e9) printed:This is my fault from #19635 🤦♂️ . Double, because I thought to run the command but clearly didn't do it before the final merge.
But, it reveals an interesting thing about
genstringsand our ongoing effort to lint strings in CI (see Automattic/a8c-ci-toolkit-buildkite-plugin#36, #19624, #19553), namely yet another piece of early feedback point we can give to developers.The current implementation, evidently, doesn't pick this up, because
genstringsdoesn't throw this as an error. At least, I'm pretty sure that's the explanation because ifgenstringsfailed so would the action. cc @AliSoftware I think we should update the action to capture this particular case and treat it as an error. What do you think? If that sounds good, I'll add it to my list.Testing
Running
bundle exec fastlane generate_strings_file_for_glotpress skip_commit:trueon this branch should not print any warning.Regression Notes
RELEASE-NOTES.txtif necessary. N.A.