feat: remove legacy support for selecting target files based on their extensions

Author: dukeluo

docs/rules/filename-naming-convention.md

@@ -49,7 +49,7 @@ In addition to the built-in naming conventions, you can also set custom naming p
 
 :warning: :warning: :warning:
 
-**Versions below v1.2.0 can only select files by using their extensions. All `v1` versions will have this feature, but is will be removed in the future. Please select your target files by the file path. For example, using `**/*.js` instead of `*.js` to select all `js` files.**
+**v1 versions have the legacy support for selecting target files based on their extensions. This legacy support has been removed since v2.0.0. Please select your target files by their file path. For example, using `**/*.js` instead of `*.js` to select all `js` files.**
 
 
 ### Options

lib/rules/filename-naming-convention.js

@@ -70,22 +70,12 @@ module.exports = {
         const filename = getFilename(filenameWithPath);
 
         for (const [fexPattern, namingPattern] of Object.entries(rules)) {
-          const matchResult =
-            matchRule(
-              filenameWithPath,
-              fexPattern,
-              getBasename(filename, ignoreMiddleExtensions),
-              namingPattern
-            ) ||
-            // legacy support for version below v1.2.0
-            // file only can be specified by fex pattern, not by file path pattern
-            // it's a legacy feature, will be removed in the future
-            matchRule(
-              filename,
-              fexPattern,
-              getBasename(filename, ignoreMiddleExtensions),
-              namingPattern
-            );
+          const matchResult = matchRule(
+            filenameWithPath,
+            fexPattern,
+            getBasename(filename, ignoreMiddleExtensions),
+            namingPattern
+          );
 
           if (matchResult) {
             const { path, pattern } = matchResult;