Closed vegerot closed 6 months ago
A better version of this diagnostic would be to check for non-null assertions, which are incorrect.
undefined?.a!.b
Fixed in Git commit 434d08514d2ab0bc70b5ecb40f1e1e7c1256b6ae. I will ship the fix in version 3.2.0.
Fix released in version 3.2.0.
minimal example:
quick-lint reports:
using a '.' after a '?.' might fail, since '?.' might return 'undefined'.
, however this is not true.Running the above code shows that optional chaining short-circuits the entire property access expression to
undefined
, not just the first property access.idk if there's a "correct" version of this diagnostic, or if we should just delete the whole thing