Fix issues with ESLint Import Resolver #103
Merged
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.
Description
Fixes issues that have resulted in the implementation of the following changes when all brought into a single branch:
The change to the way ESLint config is used and implemented in the current release is not managed the same way in the proposed
1.3
release, meaning there has been a conflict in process for generating that ESLint config. TypeScript will need to set the project and accurate directory mappings for the TypeScript Resolver in the ESLint config to ensure the that the correct directories are being targeted. As a result of the changes, these mappings were incorrect in active use and in unit testing were partly non-existant.Change Log