when TS does its job and team mates complaining that TS is too sensitive!

it does its job you douche, now you do yours!

Do they actually want their code to contain undetected bugs due to mismatched types?
What other reason would someone have to complain about TS being too sensitive?
I don‘t get it.

JS dev, just starting TS :

TS : "Oh type error here dude, that's not a string, it's an array"

Dev : "<any>", creates a PR
"Fixed issue with TS"

/facepalm.

As reviewer I reject (not comment, reject) any PR containing <any>

It was actually 'something' is string, boolean expected.

So I told them to fix it - nope, that was written 5 months ago! Too many places to fix!

Like I care!

And I constantly got complaints from the dude how js/ts is shite tech, contantly bitching is not gonna do anything, you could spend that time actually learning how to use it!

I am not saying that js/ts is great but its there, in the browser and we do use it for our app, so dude, deal with it or gtfo!

@NoToJavaScript i just reject that shit with the link to the ts docs, read it here and apply the changes!

Fucking hate rockstar brogrammers with 'clever' code. Yeah I want 5 additional layers of abstraction so I don't know where that came from and have to stack trace it, also same dude: i will just put any here!