fix(no-unlocalized-strings): recognize t() function call syntax

The t macro can be used both as tagged template (t`Hello`) and as
a function call with object syntax (t({ message, context })). Only
the tagged template was recognized, causing false positives for the
object syntax used to provide translator context.

Author: swernerx

src/rules/no-unlocalized-strings.test.ts

@@ -41,6 +41,11 @@ ruleTester.run("no-unlocalized-strings", noUnlocalizedStrings, {
     { code: '<Select value={gender} male="He" female="She" other="They" />', filename: "test.tsx" },
     { code: '<SelectOrdinal value={pos} one="#st" two="#nd" few="#rd" other="#th" />', filename: "test.tsx" },
 
+    // Inside t() function call with object syntax (not just tagged template)
+    { code: 't({ message: "Hello World" })', filename: "test.tsx" },
+    { code: 't({ message: "e.g., Philippe L.", context: "placeholder for full name field" })', filename: "test.tsx" },
+    { code: 't({ id: "msg.hello", comment: "Greetings at homepage", message: "Hello World" })', filename: "test.tsx" },
+
     // Inside msg/defineMessage
     { code: 'msg({ message: "Hello World" })', filename: "test.tsx" },
     { code: 'defineMessage({ message: "Save changes" })', filename: "test.tsx" },

src/rules/no-unlocalized-strings.ts

@@ -64,8 +64,8 @@ const LINGUI_TAGGED_TEMPLATES = new Set(["t"])
 /** JSX components from Lingui that handle localization */
 const LINGUI_JSX_COMPONENTS = new Set(["Trans", "Plural", "Select", "SelectOrdinal"])
 
-/** Function-style macros from Lingui */
-const LINGUI_FUNCTION_MACROS = new Set(["msg", "defineMessage", "plural", "select", "selectOrdinal"])
+/** Function-style macros from Lingui (t can be both tagged template and function call) */
+const LINGUI_FUNCTION_MACROS = new Set(["t", "msg", "defineMessage", "plural", "select", "selectOrdinal"])
 
 /**
  * Checks if a symbol originates from a Lingui package using TypeScript's type system.