Bug for Javascript expressions where comma is used to separate expressions

Clean Code Report False-positive / False-negative...
1

We are seeing this bug for Javascript files where a comma is used to separate expressions instead of a semicolon:
We get this finding:
“Expected an assignment or function call and instead saw an expression”
Example, which is giving the bug but is valid Javascript:
x = 1, y = 2;
instead of:

x=1;
y=2;
2

Hi,

This case should not be reported (see here) and I can’t reproduce as well.

You might be using older version of SonarQube. If it’s not the case please provide better reproducer and details of your analysis and installation.