Skip to content

Add option to use @iobroker/eslint-config #1120

@foxriver76

Description

@foxriver76

At

{ message: "ESLint", hint: "(recommended)" },
devs already get recommended to use eslint. We currently have a lot of different configs across the project, hence we created a generalized eslint config for iobroker projects.

If a dev chooses to use eslint, it should either use the centralized eslint config automatically or ask like Dou you want to configure eslint by yourself or use the official ioBroker eslint config?. In the end the ioBroker config can also be overriden and should be a good base. For React and ESM there are some extra options which can also be found in the README.md. Also a Migration guide is available that can be used here to see the changes needed in the templates. Enhance tests to have both variants depending on the new choice.

The new project and how it is added can be found at https://github.com/ioBroker/ioBroker.eslint-config

The above mentioned additional question should also contain "receommended" and should auto select the use of the new package

Additional information when the eslint-config package is used:

All dependencies to eslint(-) and prettier(-) should be removed.
Config fiels shoudl be adapted

The extension
"esbenp.prettier-vscode"
should be added to vscode extensions for typescript adapters (or ev. for all repositories).

Otherwise issues reported by standard @iobroker/eslint-config are not visible / reported directly inside vscode editor

Metadata

Metadata

Assignees

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