"strict": true a cikin tsconfig.json yana bugi jerin duk kyakkyawan bincike a lokaci guda. Ana ba da shawarar sosai ga duk sabuwar ayyuka — yana kama maye da TypeScript akwai don hana.
json
{ "compilerOptions": { "strict": true } }
"strict": true a cikin tsconfig.json yana bugi jerin duk kyakkyawan bincike a lokaci guda. Ana ba da shawarar sosai ga duk sabuwar ayyuka — yana kama maye da TypeScript akwai don hana.
{ "compilerOptions": { "strict": true } }
// strictNullChecks — null/undefined are no longer assignable to everything
let name: string = null; // ❌ Error (without strict this compiles, then crashes)
function f(u?: User) { u.name; } // ❌ u is possibly undefined → forces a check
// noImplicitAny — parameters with no inferable type must be annotated
function g(x) {} // ❌ Error: 'x' implicitly has type 'any'
// strictPropertyInitialization — class fields must be initialized
class C { name: string; } // ❌ must init in constructor or mark optional
strictNullChecks shine babbar daya: yana raba null/undefined daga wasu nau'i, sabili da haka mai-tsohuwa ya tilasta ka jigawa "yin iya rashin kasua" a ko'ina — cire #1 gida na saurin kudu errors ("ba za a iya karantawa property a undefined").
Ya fadi flags iya a hankali (strictNullChecks farko), daidaita kudu file-by-file, maimakon ba da dala komai lokaci guda a babbar tsoffin aiki.
Ba tare da strict mode, TypeScript har yanzu yana ba da dala da yawa maras aminci patterns da shi nufin ya hana (implicit any, ba-bincikun nulls).
Strict mode shine inda TypeScript yana samar da mafi girman daraja - gyara ta zama default kuma kuma kwantance flags gida da kyau horo.