feat: Add eslint config file support #85
Merged
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
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.
Use Oxlint config files for icons and JSON schemas.
Use Eslint and Oxlint config files for triggering language server restarts when the config file changes.
If a user has the Oxc plugin but not the Eslint plugin, then they will likely have a lesser experience if they try to use an Eslint file. I think this is reasonable, but we could also come up with something more complicated if desired. For example, check if the Eslint plugin is enabled and if not we could treat an Eslint config file the same as an Oxlint config file (Oxlint icon, Oxlint JSON schema).