eslint-plugin-use-agnostic 2.0.4 → 2.0.6

package/library/directive21/_commons/rules/import-rules.js

@@ -88,6 +88,8 @@ In this context, {{ ${specificFailure} }} `,
     const rootPath = /** @type {string | undefined} */ (
       context.settings.eXtraJSX?.rootPath
     );
+    console.debug("context.settings are:", context.settings);
+    console.debug("context.settings.eXtraJSX are:", context.settings.eXtraJSX);
     console.debug("reactFolder is:", reactFolder);
     console.debug("rootPath is:", rootPath);
 

package/library/index.js

@@ -205,10 +205,24 @@ export const defineDirective21 = (reactFolder) => {
  */
 export const defineConfigSettings = ({ reactFolder, rootPath }) => {
   /**
-   * @type {["**\/*.js"]}
+   * @type {["**\/*.tsx", "**\/*.ts", "**\/*.mtsx", "**\/*.mts", "**\/*.ctsx", "**\/*.cts", "**\/*.jsx", "**\/*.js", "**\/*.mjsx", "**\/*.mjs", "**\/*.cjsx", "**\/*.cjs"]}
    * The dummy file paths used by the eXtra JSX VS Code extension are JavaScript file paths, therefore this glob pattern is enough to work in recognizing the dummy file paths in order to retrieve the settings.
+   * Now that the settings are actually used in eslint-plugin-use-agnostic, they need to cover all JS/TS/JSX/TSX files.
    */
-  const files = ["**/*.js"];
+  const files = [
+    "**/*.tsx",
+    "**/*.ts",
+    "**/*.mtsx",
+    "**/*.mts",
+    "**/*.ctsx",
+    "**/*.cts",
+    "**/*.jsx",
+    "**/*.js",
+    "**/*.mjsx",
+    "**/*.mjs",
+    "**/*.cjsx",
+    "**/*.cjs",
+  ];
 
   return {
     files,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eslint-plugin-use-agnostic",
-  "version": "2.0.4",
+  "version": "2.0.6",
   "description": "Highlights problematic server-client imports in projects made with the Fullstack React Architecture.",
   "keywords": [
     "eslint",