Skip to content
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.

Optional syntax throws "no-undef" in 8.2.2+ #633

Closed
gabaum10 opened this issue Jun 14, 2018 · 3 comments
Closed

Optional syntax throws "no-undef" in 8.2.2+ #633

gabaum10 opened this issue Jun 14, 2018 · 3 comments

Comments

@gabaum10
Copy link

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

@richardgirges
Copy link

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.

@lehni
Copy link

lehni commented Jul 4, 2018

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

@lehni
Copy link

lehni commented Jul 4, 2018

@existentialism you can probably close this issue here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants