eslint-config-prettier: conflicts with standard/computed-property-even-spacing

I’m using eslint-config-prettier together with eslint-config-prettier-standard which works great except for this:

prettier wants

    const { whatever } = loooooooooooooooooooooooong[
      something
    ].some.thiiiiiiiiiiiiing[0]

while standard wants

    const { whatever } = loooooooooooooooooooooooong[something].some.thiiiiiiiiiiiiing[0]

I wonder if this is due to computed-property-even-spacing not being turned off.

eslint-config-prettier-check reports “No rules that are unnecessary or conflict with Prettier were found.”

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 5
Comments: 15 (4 by maintainers)

Commits related to this issue

Update to eslint-config-prettier@2.5.0 ... which adds exclusions for eslint-plugin-standard. See https://github.com/prettier/eslint-config-prettier/issues/29 — committed to lydell/eslint-config-prettier-standard by lydell 7 years ago

Most upvoted comments

Thanks!

That rule is already turned off: https://github.com/prettier/eslint-config-prettier/blob/0f131661f718e278ec1e51529f56450a61f10b11/standard.js#L6

So it’s strange that you had to turn it off manually. Perhaps you forgot to enable standard support?

{
  "extends": [
    "standard",
    "prettier",
    "prettier/standard" // Perhaps you forgot this line?
  ],
  "plugins": [
    "standard"
  ],

+12

lydell on Feb 26, 2018

Tip: Don’t include prettier in extends array. Just prettier/standard to disable Standard rules that directly conflict with Prettier (not much).

This way you get as much Standard and as little Prettier as possible.

You also don’t need eslint-plugin-prettier.

corysimmons on Apr 10, 2019

Dunno. Packages keep getting updated and Standard/eslint/Prettier/editor-plugins have turned into a huge headache to get working together, so I just uninstalled all that crap months ago, and just use VSCode’s default Prettier integration for generic code style rules.

Now I actually get work done and products launched.

corysimmons on Apr 10, 2019

Can confirm that that configuration fixes the described problems, thanks a lot! (Sorry for being vague at the beginning again)

On Mon, Feb 26, 2018 at 6:00 PM Francisco Guijarro franleplant@gmail.com wrote:

Oh, I didn’t knew that, that’s probably it, thanks a lot!!!

On Mon, Feb 26, 2018 at 5:38 PM Simon Lydell notifications@github.com wrote:

Thanks!

That rule is already turned off:

https://github.com/prettier/eslint-config-prettier/blob/0f131661f718e278ec1e51529f56450a61f10b11/standard.js#L6

So it’s strange that you had to turn it off manually. Perhaps you forgot to enable standard support?

{ “extends”: [ “standard”, “prettier”, “prettier/standard” // Perhaps you forgot this line? ], “plugins”: [ “standard” ],

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/prettier/eslint-config-prettier/issues/29#issuecomment-368641895, or mute the thread https://github.com/notifications/unsubscribe-auth/ABxEJ1OUMHSWa5ASntAgCII1sXsIOno1ks5tYxZAgaJpZM4PYLMo .

franleplant on Feb 26, 2018

@franleplant Can you make a VR app that lets me see through your eyes? 😃

lydell on Feb 26, 2018