You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing frameworks that have localized strings, it's really easy to forget the bundle: parameter to NSLocalizedString. Unfortunately this isn't something that can be solved in code; adding my own override of NSLocalizedString for the bundle-less case trips up genstrings, and adding a custom function with a different name isn't compatible with xcodebuild -exportLocalizations.
The goal of the rule here is to catch all calls to NSLocalizedString and enforce that the bundle: parameter is present. It doesn't matter what the value is, it should just be specified.
This would be opt-in. I don't think there's any configuration for it.
The text was updated successfully, but these errors were encountered:
New Issue Checklist
New rule request
When writing frameworks that have localized strings, it's really easy to forget the
bundle:
parameter toNSLocalizedString
. Unfortunately this isn't something that can be solved in code; adding my own override ofNSLocalizedString
for the bundle-less case trips upgenstrings
, and adding a custom function with a different name isn't compatible withxcodebuild -exportLocalizations
.The goal of the rule here is to catch all calls to
NSLocalizedString
and enforce that thebundle:
parameter is present. It doesn't matter what the value is, it should just be specified.This would be opt-in. I don't think there's any configuration for it.
The text was updated successfully, but these errors were encountered: