spread operator throws off js syntax recognition

Issue by Savacken Wednesday Feb 17, 2021 at 19:20 GMT Originally opened as https://github.com/adobe/brackets/issues/15321

Prerequisites

[x] Can you reproduce the problem with Debug -> Reload Without Extensions?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?
[x] Did you read the Troubleshooting guide?

Description

Depending on how / where it's used, the spread operator in js files seems to break Brackets' ability to correctly interpret syntax.

Steps to Reproduce

create a new js file
add code similar to;
```
let x = { y: 1 };
let z = {
...x,
};
console.log(`${y.z}`);
// comment
```
If you paste that in notice the syntax highlighting in the lines after the spread operator. If you type it in, the console.log line indents after the line break as if something above it is malformed.

With some experimenting I found that if the entire z declaration is on a single line, let z = { ...x }; then things seem to be okay. You can also get it to be kind of okay on a multiline declaration if a property follows the spread operator's inclusion; i.e.

let z = {
  ...x,
  a: 'A',
 };

By "kind of" I mean that the highlighting of the console.log line seems okay, but the highlighting of the a property is still a little off.

ESLint isn't having a problem with the code that Brackets doesn't recognize.

Expected behavior: [What you expected to happen] Brackets to correctly highlight / recognize code following valid use of a spread operator.

Actual behavior: [What actually happened] See description above in how to reproduce, but a simple recap, depending on how the spread operator is used Brackets seems to not recognize the syntax.

Versions

Behaves the same in both Brackets 14.1 and 14.2.

MacOS 10.15.7

brackets-archive / bracketsIssues