localizedStringRoutines option missing for UncommentedLocalizedString and HardcodedUIString
Issue #102
new
The "Uncommented localized string" and "UI String not localized" rules should both have the "Functions used in place of NSLocalizedString" option, but do not.
(Originally reported by @brian_dorfman at #101)
Comments (1)
-
reporter - Log in to comment
The “UI String not localized” rule should work correctly “out of the box” even without having to specify the name(s) of your custom L10N function, so it doesn’t really need this option.