Added editor settings converter for tslint.configFile, with full settings access #652
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.
PR Checklist
status: accepting prs
Overview
The VS Code TSLint extension allow for a custom configuration path other than
tslint.json
viatslint.configFile
. Now, if that exists in the original editor settings and matches the directory name of the output ESLint file path, the new ESLint editor settings will include the output ESLint file path.This logic necessitated adding
settings: TSLintToESLintSettings
as an argument toEditorSettingConverter
s. Otherwise the file diff is actually not that big 😉.