Support option chaining syntax highlighting

[mjbvz]

TS and JS Grammar Extension version: 0.0.22 / latest

From microsoft/vscode#34776 (comment)

Feature request
Support highlighting the proposed option chaining syntax for JS/TS

const a = {
  b: {
    c: {
      d: {
        e: 1,
        g: [1, 2, 3],
      },
    },
    f: null,
  },
};

const brokenSyntaxHighlighting = () => {
  const array = a?.b?.c?.d?.g;

  /**
   * No TypeEror, but syntax highlighting is broken
   */
  const test = a?.b?.f?.f;

  for (let i = 0; i < array.length; i++) {
    console.log(array[i]);
  }
};

brokenSyntaxHighlighting();

TS support for this is tracked by: microsoft/TypeScript#16

[sheetalkamat]

This feature is still in stage 1. Will look at it once it gets into stage 3

[zalishchuk]

@sheetalkamat Is it really hard to implement syntax support for this feature? We have to use something like idx for these purposes which is not always convenient.

[oychao]

I need this very hardly.

[zalishchuk]

@sheetalkamat can you please update https://github.com/sheetalkamat/TypeScript-TmLanguage-VsCode?

[fungilation]

Time to revisit this, with React Native 56 integrating optional chaining support, now in babel 7.

This is the best thing about coffeescript and so much more convenient than the verbose alternative. But broken syntax highlighting in VSCode is getting in the way of full adoption.

[mehulmpt]

Well currently you can sort of get around this by disabling VSCode's internal javascript linter and using something like eslint, but obviously you lose some features of vscode linter like dimming of unused variables/imports, etc.

[fungilation]

I see in my VSCode default config:

"eslint.enable": true,

Which tells me eslint is already the default VSCode linter? If not, how would you turn off the internal js linter?

EDIT: I see this in settings is to turn off internal js validation, and I already have:

"javascript.validate.enable": false,

[mjbvz]

This repository only handles syntax coloring. Semantic understanding of chaining is tracked by microsoft/TypeScript#16

[jabsatz]

Babel 7 has been released with the optional chaining operator as a plugin, is there any chance of revisiting this?

[daix6]

This feature is still in stage 1. Will look at it once it gets into stage 3

It's time!!

[bondparkerbond]

Optional Chaining is officially in Stage 3. Should this issue be reopened?

[spassvogel]

Please consider to implement this.

[orta]

I agree, I think it's time this should get re-opened