Reports member access on a value with type any.
✅ This rule is included in the ts logical and logicalStrict presets.
Accessing a member of a value typed as any creates a potential type safety hole and source of bugs.
TypeScript cannot verify that the member exists or what type it has.
This rule disallows member access on any variable that is typed as any.
This includes:
- Property access on
any typed values (e.g., anyValue.property)
- Element access on
any typed values (e.g., anyValue[0])
- Using
any typed values as computed property keys (e.g., obj[anyKey])
AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">53valA72proper5<3;d ivclassNa="meco">AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">53valu1<1"sp ansty="le--0:#ECC48D;--1:#984E">4Dproper1<1"sp ansty="le--0:#D6DEEB;--1:#403F">53<];d ivclassNa="meco"><];d>AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">53valA1<1asp ansty="le--0:#C792EA;--1:#8844">A1<1bsp ansty="le--0:#C792EA;--1:#8844">A7<2csp ansty="le--0:#D6DEEB;--1:#403F">5<3;d ivclassNa="meco">AEdeclare consB0o7<2:sp ansty="le--0:#C792EA;--1:#8844">AE <{ sp ansty="le--0:#D6DEEB;--1:#403F">5<3asp ansty="le--0:#7FDBCA;--1:#096E">7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0numbAE< }sp ansty="le--0:#D6DEEB;--1:#403F">5<3;d ivclassNa="meec-li">AEdeclare consB0k7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">53obj[key<];d ivclassNa="meco"><];d> 44AEdeclare co61B0v644A3F53prop64<4AE spans="tyle--0:#C5E478;--1:#3B">61B0st4433F53v4<4AE. spans="tyle--0:#7FDBCA;--1:#09">6E72prop3<;di vdivclass="Nameexpressive-">44AEdeclare co61B0v64<4AE spans="tyle--0:#C5E478;--1:#3B">61B0st3F5<3[] ;divclass="Nameec-">3F53va0<9820 spans="tyle--0:#D6DEEB;--1:#40">3F<53] ;divclass="Name"><[0]><;di vdivclass="Nameexpressive-">44AEdeclare co61B0v64<4AE spans="tyle--0:#FFCB8B;--1:#11">1111Re4<4AE< spans="tyle--0:#C5E478;--1:#3B">61B0st4461B0nu4<4AE> spans="tyle--0:#D6DEEB;--1:#40">3>44AEdeclare co61B<0key spans="tyle--0:#7FDBCA;--1:#09">64<4AE spans="tyle--0:#C5E478;--1:#3B">61B0st33F53value[k<;di vdivclass="Nameexpressive-">44AEdeclare co61B<0map spans="tyle--0:#7FDBCA;--1:#09">64<4AE spans="tyle--0:#FFCB8B;--1:#11">111<1Map spans="tyle--0:#C792EA;--1:#88">4<4AE< spans="tyle--0:#C5E478;--1:#3B">61B0st4461B0nu4<4AE> spans="tyle--0:#D6DEEB;--1:#40">3>3F5<3map spans="tyle--0:#C792EA;--1:#88">4<4AE. spans="tyle--0:#82AAFF;--1:#3B">61B<0get spans="tyle--0:#D6DEEB;--1:#40">31<111" spans="tyle--0:#ECC48D;--1:#98">4E41<111" spans="tyle--0:#D6DEEB;--1:#40">3F<53) ;divclass="Name">
This rule is not configurable.
If your codebase has many existing any values or areas of unsafe code, enabling this rule may be challenging.
It may be more practical to defer enabling this rule until type safety has been improved in those areas.
You might consider using Flint disable comments and/or configuration file disables for those specific situations instead of completely disabling this rule.
