Commas are generating warnings

[funder7]

Describe the bug
When opening a JDL in VS Code, a comma inside of a comment will cause a warning to show up with "Useless commas can be removed" as the cause.
Exporting a JDL with the jhipster export-jdl command, generates comma separated fields in entities, and fields are highlighted as warnings too (same reason).

To Reproduce
Steps to reproduce the behavior:

1. Create a JDL file
2. Create two entities
3. First entity: create two fields, separating them with a comma
4. Second entity: create two fields, without the comma separating them
5. Add a JavaDoc comment for each field, containing commas
6. Add a normal comment (//) containing commas
7. Comma separated fields will be highlighted as warning
8. JavaDoc comments containing commas will be highlighted as warning

Expected behavior

• Comments containing commas must never be highlighted as a warning
• If fields must not be comma separated, then jhipster-generator should not export JDL files like that.
• As the JDL seems to work with comma separated fields, letting the user choose to use them or not could be a solution.

Screenshots

Different situations that are causing warnings to show up (or not)

Desktop (please complete the following information):

• OS: elementaryOS 5.1 (ubuntu 19.04 LTS based)
• VS Code: 1.45.1
• VS Code JHipster JDL extension : 2.2.0

Additional info
I suppose that comments are being parsed with the same rule-check used for comma separated fields. That souldn't happen!

[colameo]

thanks for reporting this! will be fixed in the next release.

[colameo]

so it's fixed:

however, if a comma appears in one field definition all fields are marked (note the last field with comments):

please note that you can also disable linting warnings by putting at the very first line of your JDL a comment as follows:

// no-linting

or

// lint = false

one more thing, do not use commas as they will be removed in the near future (see also)

[funder7]

That's a fast fix! :-)

I think that if commas will be removed in the next release, then there will be introduced a new warning telling to not use them in field definitions, so that would solve the last problem you reported.

But disabling linting wouldn't disable it for all rules?