feat: add support for flat configs #1503
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Feb 13, 2024
|
🎉 This issue has been resolved in version 27.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Something of a revive of #1245, I was looking into upgrading to
@typescript-eslintv6 and realised effectively we should move off using therecommendedproperty inmeta.docswhich in turn means changing how we build our configs and thus "we might as well try doing flat config first".I'm opening this as a draft for visibility - there's still some follow up to do including updating the docs, actually removing the dynamicness in favor of a static list, and reviewing the latest migration docs to see if there's anything new we need to account for.
Also in particular I'm not thrilled we're listing specific file types in our recommended config now - I wouldn't be surprised if that's easy to change downstream, but I want to look more into that in particular.
@SimenB do you have any feelings about doing a next prerelease vs just landing this? I'll try to test this out but everything's a bit of a mess right now...
Resolves #1408