Skip to content

Conversation

@JoshuaKGoldberg
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg commented Jul 5, 2019

PR Checklist

Overview

The original ESLint configuration is now included in the writeConversionResults written file with a single ....

Additionally skipped outputting rules that match an existing ESLint plugin. If an extended ESLint plugin defines a rule with the same values as the resultant config, the config will skip printing it.
This necessitated expanding "failures" to allow a new ConfigurationError type of error for unfound ESLint configurations.

Renames "packages" in the configuration reading/converting logic areas to "plugins", as that's what ESLint calls them.

Josh Goldberg added 3 commits July 5, 2019 09:33
The original ESLint configuration is now included in the `writeConversionResults` written file with a single `...`.

Additionally skipped outputting rules that match an existing ESLint plugin. If an extended ESLint plugin defines a rule with the same values as the resultant config, the config will skip printing it.
This necessitated expanding "failures" to allow a new `ConfigurationError` type of error for unfound ESLint configurations.

Renames "packages" in the configuration reading/converting logic areas to "plugins", as that's what ESLint calls them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Apply eslintrc before factoring in list of eslint plugins Don't include rule flags that are the same as plugins

2 participants