parse5

parse5 copied to clipboard

We should enable the rule to disallow non-null assertions:

foo!.bar!.baz;

from what i remember, we have quite a lot of these scattered around because of the whole "bootstrap" concept. many methods make assumptions around which methods ran before them, meaning we "know" the value shouldn't be null, but technically it could.

in all those cases, we should either add null checks (usually throwing if it is null) or rework the bootstrapping to happen in the constructor (feel like @fb55 mentioned something similar to that a while ago).