Resolve `strict-boolean-expressions` ESLint warnings
Background / User story
With #1512 (closed) we introduced the TypeScript extensions for the ESLint Standard preset that we use.
Because one of the new rules is not trivial to address, we decided to soften it into just warnings and tackle it at a later point. This issue is about doing exactly that.
What to change
- Design: N/A
- Research: N/A
- Spec: N/A
- Legal: N/A
-
Development:
- Rough idea: Fix issues for trivial changes and disable rule for non-trivial changes.
Hints for testers
While this in theory does not alter the behavior of the extension, it still touches a lot of code. So, I think it is sadly necessary to test the extension to make sure it still behaves as it should.
Affected areas of the extension are: IPM, premium, allowlisting, the options page, gathering of version information and various core functionalities – basically a lot of small things spread throughout the code :/
Everything should behave the way it used to do. However, there is one logic change: The values 0
, false
and null
are no longer considered valid domainList
s or licenseStateList
s for the IPM system.
Hints for translators
Nothing to translate.