Comment inside an object literal treated as whitespace, triggering a false positive standard/object-curly-even-spacing

[lolmaus]

Hey.

Got this code which I consider stylistically fine:

import {belongsTo/*, hasMany*/} from 'ember-data/relationships'

I can put the caret anywhere inside the comment and hit Ctrl+Shift+/ to have it uncommented. Very efficient.

The code triggers this error:

Expected consistent spacing (standard/object-curly-even-spacing)

I believe it should not trigger this error, unless there's stray whitespace after */.

Please fix. 🙇

[Krinkle]

Same issue for the following, using the default setting of either. Complains about there being two spaces between the value and the closing bracket instead of one, presumably because it ignores the comment.

var intuition = lib.fetch({ url: loadUrl, timeout: 7000 /* foo bar */ });

[xjamundx]

Thanks for these, I don't really intend to fix these as it looks like standard is going to pick some standard for curly braces and array brackets AFAIK

[feross]

@xjamundx Yes, that's the plan.

[feross]

Closing as this rule will be changed in a future version of standard, hopefully 11.x or 12.x.