Basically you are saying: "I know what I'm doing, leave me alone."
But typescript only ever checks at compile time, never at runtime, so when you get back something else, a lot of assumptions in your code will go away.
It's better to check for undefined/null values if typescript tells you.
Which is also very convinient by using the operators introduced for that, like ?., ?? etc.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would say that
!is as dangerous asas Xyz.Basically you are saying: "I know what I'm doing, leave me alone."
But typescript only ever checks at compile time, never at runtime, so when you get back something else, a lot of assumptions in your code will go away.
It's better to check for
undefined/nullvalues if typescript tells you.Which is also very convinient by using the operators introduced for that, like
?.,??etc.