Support Optional Chaining in Typescript Parser

[justinmwarner]

What code were you trying to parse?

// Please put code here
  const obj = {name: ""};
  return {
    name: obj?.name,
    ...additionalData,
  };

What did you expect to happen?
No error, parses fine, and shows in IDE fine.

What actually happened?

Versions

package	version
@typescript-eslint/parser	^2.3.1
TypeScript	^3.7.0-dev.20191002
ESLint	6.1.0
node	10.16.3
npm	6.9.0

Expected to land in 3.7.x from Typescript-
https://github.com/Microsoft/TypeScript/wiki/Roadmap#37-november-2019
microsoft/TypeScript#33294

Relates to #136

[AlCalzone]

This breaks Prettier auto-formatting too, if that is done via eslint.

[bradzacher]

3.7 beta was only just released (and the PRs for nullish coalescing / optional chaining were only merged a few days ago).

Please give us some time to add the features.

duplicate #1033

[AlCalzone]

No worries, just thought you might want to know the implications.

[matiishyn]

any updated on this one?

[justinmwarner]

any updated on this one?

@matiishyn , look at #1033 , looks like eslint is good to go, prettier is still working on it. See the other ticket for the prettier items.