Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ESLint flat config #376

Open
bmish opened this issue Dec 28, 2022 · 1 comment
Open

Support ESLint flat config #376

bmish opened this issue Dec 28, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@bmish
Copy link
Owner

bmish commented Dec 28, 2022

Need to investigate how close we can support plugins that export flat configs.

How can we detect flat configs exported by a plugin so we can determine which rules are part of which configs?

https://eslint.org/blog/2022/08/new-config-system-part-2/

@bmish
Copy link
Owner Author

bmish commented Feb 19, 2024

Per eslint/eslint#18095 (comment), ideally plugins would continue to use the exported configs object to contain all their configs, both legacy and flat (temporarily using flat/ prefixes for flat configs before moving to -legacy suffixes for legacy configs). I'm not sure there's much we can or should do to detect flat configs that some plugins are exporting with string exports like eslint-plugin-example/configs/recommended. Plugins should eventually consolidate those back into the configs object.

We can update our README with documentation about this.

There's also a possibility that, using the configs object, we could detect the flat/legacy versions of the same config, and add some smart behavior to distinguish them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant