Babel-eslint: Optional syntax throws "no-undef" in 8.2.2+

Created on 14 Jun 2018 · 3Comments · Source: babel/babel-eslint

Take the following code:

   const test = {
        a: 'test string'
    };

    console.log(test.a?.b);

In [email protected]+ b is throwing a no-undef error. Downgrading to 8.2.1 does not. Previously reported in #511

Source

gabaum10

👍2

Most helpful comment

Still seeing this behavior as well on every version of babel-eslint after 8.2.1 (including the master branch). Not sure why #511 was closed. Downgrading doesn't seem like an acceptable solution.

richardgirges on 19 Jun 2018

👍3

All 3 comments

Still seeing this behavior as well on every version of babel-eslint after 8.2.1 (including the master branch). Not sure why #511 was closed. Downgrading doesn't seem like an acceptable solution.

richardgirges on 19 Jun 2018

👍3

This got addressed in #595, but I am seeing new problems with 8.2.4 and 8.2.5 now: #643