Typescript lint what's the proper way to declare any type with "no-any": true

Question

I want to use gts in my project.

It has the rule in tslint.json "no-any": true. That rule totally forbids using any keyword anywhere in the code. What's the common use case of dealing with it function can accept any type. I'm aware that I can override this rule. But I wonder how would someone handle the situation when e.g. function that executes sql accepts arguments of different types. Is there best practices to handle this case?

The only thing that comes in mind is to specify all primitives types via |

param: string| number| Date;

But what if I'm wrapping some external code e.g. mysql in my function that already accepts any[].

How about `unknown`? https://stackoverflow.com/questions/51439843/unknown-vs-any/51439876#51439876 — Titian Cernicova-Dragomir, Mar 18 '19 at 10:26
@TitianCernicova-Dragomir yep, unknown works great, if you answer the question I'll accept it. — deathangel908, Mar 19 '19 at 08:47

score 2 · Accepted Answer · answered Mar 19 '19 at 08:53

I think most cases should be covered well by unknown. unknown is a safer alternative to any. The basic idea is you can assign anything to unknown just like any, but unlike any you can't do much with unknown without explicit checks or type assertions which is probably what you want (see here for details).

You might still encounter corner cases where unknown can't just replace any (type parameters with function constrains under strictFunctionTypes come to mind), but it should generally work.

Typescript lint what's the proper way to declare any type with "no-any": true

1 Answers1