Skip to content

Suggestion: add a recommended config #35

@marcalexiei

Description

@marcalexiei

What is the problem this feature would solve?

Right now the following ESLint configurations located in examples repo:

have a lot of shared content (basically all the last object).
I performed 2 quick searches with part of it:

What is the feature you are proposing to solve the problem?

Export a new recommended config containing the code shared among the various examples could:

  • reduce maintenance efforts
  • allow user to adopt and keep up to date with the suggested practices more easily.

If you are interested I can work on a PR.

What alternatives have you considered?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions