Skip to content

Why not combine "prettier/*" configs to one? #173

@thorn0

Description

@thorn0

Add extra exclusions for the plugins you use like so:
extends: ..., "prettier/@typescript-eslint", "prettier/babel" ...

I think this step unnecessary complicates things for beginners. Why simply not have one big config prettier containing all those rules from prettier/* set to off. I was sure this was done out of technical necessity. I thought ESLint would error on unknown rules if you use prettier/react without the react plugin, but turns out it's not the case. ESLint (I tested 6.x and 7.x) is perfectly okay with unknown rules in the config if they're set to off. So why the complexity? (Truly sorry if already discussed.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions