Using non-null assertions cancels out the benefits of strict null-checking, and introduces the possibility of runtime errors. Avoid non-null assertions unless absolutely necessary. If you still need to use one, write a skipcq comment to explain why it is safe.
Occurrences
There are 2 occurrences of this issue in the repository.
Description
Using non-null assertions cancels out the benefits of strict null-checking, and introduces the possibility of runtime errors. Avoid non-null assertions unless absolutely necessary. If you still need to use one, write a skipcq comment to explain why it is safe.
Occurrences
There are 2 occurrences of this issue in the repository.
See all occurrences on DeepSource → app.deepsource.com/gh/Ajay-Dhangar/CodeMastermindHQ/issue/JS-0339/occurrences/