From 7e068fad3ce6cc73bcedfc41835a3931c9a0b213 Mon Sep 17 00:00:00 2001
From: "Ben Neoh [SSW]" <87377903+Ben0189@users.noreply.github.com>
Date: Thu, 15 Aug 2024 14:42:58 +1000
Subject: [PATCH] =?UTF-8?q?XS=E2=9C=94=20=E2=97=BE=20update=20typescript?=
 =?UTF-8?q?=20config=20rules=20(#9016)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

update typescript config rules

Add details for "noImplicitAny" setting
---
 rules/good-typescript-configuration/rule.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rules/good-typescript-configuration/rule.md b/rules/good-typescript-configuration/rule.md
index 90c9d3e05d4..8c40c02c2e3 100644
--- a/rules/good-typescript-configuration/rule.md
+++ b/rules/good-typescript-configuration/rule.md
@@ -26,7 +26,7 @@ Putting a “tsconfig.json” file in your project tells the typescript compiler
 
 ### Disable implicit “any”
 
-The primary benefit of TypeScript is type-safety, and attempting to escape from the type-safety should be a conscientious decision by the developer. So ensure that noImplicitAny is true, and keep your code type-aware and able to be refactored.
+The primary benefit of TypeScript is type-safety, and attempting to escape from the type-safety should be a conscientious decision by the developer. So ensure that noImplicitAny is true, and keep your code type-aware and able to be refactored. Enabling "noImplicitAny" doesn't mean your project will never use the "any" type. You can still have "any" types if you explicitly declare them. For more on the difference between implicit and explicit typing in TypeScript, check out the [different between explicit and implicit typing](https://www.schibsted.pl/blog/typescript-type-inference).
 
 ### Exclude external files