/* eslint-disable @typescript-eslint/no-explicit-any */ 😂
yeah... AnyScript hehe
I try to avoid any as much as possible but there are times where a badly written API just breaks your arm and you are like "fiiiiiiiiine, I'll just manage edge cases when they prop up in sentry". Deploys... 20min later. "prod is down"..................
The problem is that a lot of developers don't understand why it's not good to use any - I was the same when I started. I stumbled across one video during my early learning that taught me well - by the end of the video, I said to myself "oooh that's why it's called TYPEscript". Once you get it, you'll never look back. Teaching type safety is very important, I've even seen too many component libraries that use it in sample code. There should be an emphasis on teaching why the use of any is bad practice in most cases.
I feel that just ruins why typescript should be used. Personally I like typescript and defining types, it just keeps everything clean, easier to debug code and helps to code faster.
I don't understand the purpose of typescript. Why can't you use typeof and instanceof to insure type safety? Why is there a need for a third party library?
// @ts-ignore
Something is better than nothing!
The amount of any’s in my code is criminal🤕, i will refractor eventually
Full-Stack Developer
1mo