This repository was archived by the owner on Feb 5, 2025. It is now read-only.
Remove unnecessary NSLocalizedString call(the text is already localized)
#658
Conversation
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The removed line caused a failure on
genstrings: "Argument is not a literal string." Also, the argumentsignInWithSiteCredentialsButtonTitleis already localized.I'm not sure what's the proper way to make this patch on top of 2.1.0 release. This PR goes to the trunk branch, which is same as "2.1.0" tag at the moment. If this PR is merged before any other PRs, then this will be the only change added on top of 2.1.0. I guess we could create a dedicate 2.1.1 branch just to be safe?
cc @oguzkocer