Skip to content
Flint
Blog

anyCalls

Reports calling a value with type any.

✅ This rule is included in the ts logical and logicalStrict presets.

Calling a value typed as any creates a potential type safety hole and source of bugs. TypeScript cannot verify that the value is actually a function, what parameters it expects, or what it returns. This rule disallows calling any value that is typed as any or Function.

This includes:

  • Regular function calls on any typed values
  • Constructor calls with new on any typed values
  • Tagged template literals using any typed values as the tag

The Function type behaves almost identically to any when called, so this rule also disallows calling values of type Function that have no call or construct signatures.

Examples

Section titled “Examples”
AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">B0val53(<);d ivclassNa="meco"><);d>AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">53valAB0proper53(<);d ivclassNa="meco"><);d>AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">72n5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0val53(<);d ivclassNa="meco"><);d>AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">AB0a5<3;d ivclassNa="meec-li">B0val5<3`sp ansty="le--0:#ECC48D;--1:#3B61">B0templa5<3`sp ansty="le--0:#D6DEEB;--1:#403F">5<3;d ivclassNa="meco"><`;d>AEdeclare consB0val7<2:sp ansty="le--0:#C792EA;--1:#8844">A11Functi5<3;d ivclassNa="meec-li">B0val53(<);d ivclassNa="meco"><);d>
44AEdeclare co61B0v64<4AE spans="tyle--0:#D9F5DD;--1:#11">11<11() spans="tyle--0:#C792EA;--1:#88">44AE< => spans="tyle--0:#C5E478;--1:#3B">61B0 >361B0v3F5<3() ;divclass="Name"><;di vdivclass="Nameexpressive-">44AEdeclare co61B0ob644A61B0me11<11() spans="tyle--0:#7FDBCA;--1:#09">64<4AE spans="tyle--0:#C5E478;--1:#3B">61B04433F53ob4<4AE. spans="tyle--0:#82AAFF;--1:#3B">61B0me3F5<3() ;divclass="Name"><;di vdivclass="Nameexpressive-">44AEdec344AEc31111Constru3F5<3 { }divclass="Nameec-">6E7<2new spans="tyle--0:#D6DEEB;--1:#40">361B0Constru3F5<3() ;divclass="Name"><;di vdivclass="Nameexpressive-">44AEco61B<0tag spans="tyle--0:#C792EA;--1:#88">44A1<111( spans="tyle--0:#D7DBE0;--1:#40">3F53str64<4AE spans="tyle--0:#FFCB8B;--1:#11">1111TemplateStringsA446E7<2... spans="tyle--0:#D7DBE0;--1:#40">3F53va64<4AE spans="tyle--0:#C5E478;--1:#3B">61B0unk3F<53[] spans="tyle--0:#D9F5DD;--1:#11">1<111) spans="tyle--0:#C792EA;--1:#88">44AE< => spans="tyle--0:#D6DEEB;--1:#40">3F53stri >0<9820 spans="tyle--0:#D6DEEB;--1:#40">3F<53] ;divclass="Nameec-">61B<0tag spans="tyle--0:#D6DEEB;--1:#40">361B0temp33<;di vdivclass="Nameexpressive-">44AEinter3F53 SafeFunct44AEext361B0Func3F<53 {divclass="Nameec-">de11<11() spans="tyle--0:#7FDBCA;--1:#09">6361B03344AEdeclare co61B0v64<4AE spans="tyle--0:#FFCB8B;--1:#11">1111SafeFunc361B0v3F5<3() ;divclass="Name">

Options

Section titled “Options”

This rule is not configurable.

When Not To Use It

Section titled “When Not To Use It”

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 lint disable comments for specific situations instead of completely disabling this rule.

Further Reading

Section titled “Further Reading”

Equivalents in Other Linters

Section titled “Equivalents in Other Linters”