rebase

biomejs · Oct 16, 2023 · be64ce5 · be64ce5
1 parent 93fd4a7
commit be64ce5
Show file tree

Hide file tree

Showing 12 changed files with 482 additions and 460 deletions.
diff --git a/crates/biome_js_analyze/src/analyzers/nursery.rs b/crates/biome_js_analyze/src/analyzers/nursery.rs
diff --git a/crates/biome_js_analyze/src/analyzers/nursery/no_empty_block_statements.rs b/crates/biome_js_analyze/src/analyzers/nursery/no_empty_block_statements.rs
@@ -55,7 +55,7 @@ declare_rule! {
     /// ```
     ///
     pub(crate) NoEmptyBlockStatements {
-        version: "next",
+        version: "1.3.0",
         name: "noEmptyBlockStatements",
         recommended: false,
     }

diff --git a/crates/biome_js_analyze/tests/specs/complexity/noForEach/invalid.js.snap b/crates/biome_js_analyze/tests/specs/complexity/noForEach/invalid.js.snap
@@ -36,7 +36,7 @@ invalid.js:1:1 lint/complexity/noForEach ━━━━━━━━━━━━━
     4 │ 
     5 │ (els.forEach)((el) => {
   
-  i forEach could lead to performance issue when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
+  i forEach could lead to performance issues when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
   
 
 ```
@@ -56,7 +56,7 @@ invalid.js:5:1 lint/complexity/noForEach ━━━━━━━━━━━━━
     8 │ 
     9 │ els['forEach']((el) => {
   
-  i forEach could lead to performance issue when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
+  i forEach could lead to performance issues when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
   
 
 ```
@@ -76,7 +76,7 @@ invalid.js:9:1 lint/complexity/noForEach ━━━━━━━━━━━━━
     12 │ 
     13 │ (els['forEach'])((el) => {
   
-  i forEach could lead to performance issue when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
+  i forEach could lead to performance issues when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
   
 
 ```
@@ -95,7 +95,7 @@ invalid.js:13:1 lint/complexity/noForEach ━━━━━━━━━━━━
        │ ^^
     16 │ 
   
-  i forEach could lead to performance issue when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
+  i forEach could lead to performance issues when working with large arrays. When combined with functions like .filter or .map, this causes multiple iterations over the same type.
   
 
 ```