docs: update no-undef-init when not to use section (#19624)

Tanujkanti4441 · web-flow · commit ca7a735dde44 · 2025-04-18T02:08:36.000+05:30
diff --git a/docs/src/rules/no-undef-init.md b/docs/src/rules/no-undef-init.md
@@ -80,7 +80,9 @@ class Foo {
 
 ## When Not To Use It
 
-There is one situation where initializing to `undefined` behaves differently than omitting the initialization, and that's when a `var` declaration occurs inside of a loop. For example:
+There are situations where initializing to `undefined` behaves differently than omitting the initialization.
+
+One such case is when a `var` declaration occurs inside of a loop. For example:
 
 Example of **incorrect** code for this rule:
 
@@ -150,3 +152,22 @@ for (i = 0; i < 10; i++) {
 ```
 
 :::
+
+Another such case is when a variable is redeclared using `var`. For example:
+
+```js
+function foo() {
+    var x = 1;
+    console.log(x); // output: 1
+    
+    var x;
+    console.log(x); // output: 1
+
+    var x = undefined;
+    console.log(x); // output: undefined
+}
+
+foo();
+```
+
+In this case, you can avoid redeclaration by changing it to an assignment (`x = undefined;`), or use an eslint disable comment on a specific line.
