Error E0718 is not an actual error

[Danny-06]

The error as documented in the official docs https://quick-lint-js.com/errors/E0718/
implies that the following scenario should throw an error:

const bug = { milestone: null };
console.log(bug.milestone);               // null
console.log(bug.milestone?.name);         // undefined
console.log(bug.milestone?.name.trim());  // throws an error

But the actual output when running the code is:

const bug = { milestone: null };
console.log(bug.milestone);               // null
console.log(bug.milestone?.name);         // undefined
console.log(bug.milestone?.name.trim());  // undefined

Is there a good reason for this error to be listed or should be removed?

[tomocrafter]

I faced exact same error and it should be removed imo.
eslint's no-unnecessary-condition rule https://typescript-eslint.io/rules/no-unnecessary-condition/ enforces ?. to be . after ?. and It sounds reasonable since above code won't raise an error.

[strager]

Is there a good reason for this error to be listed or should be removed?

This diagnostic should be removed. In fact, it is removed in master (#1192). I will ship the fix in version 3.2.

[tomocrafter]

@strager Thank you!
now I wonder why it is introduced first, like was it actually occurs the error?

[strager]

now I wonder why it is introduced first, like was it actually occurs the error?

Nah, my brain just wasn't working. 😄

[strager]

Fix released in version 3.2.0.