Enforce relative imports when importing from core #1616
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.
What does this change?
Adds an eslint rule to ban non-relative imports from core and replaces all instances with relative imports.
Why?
We had an issue where non relative imports were causing build failures, so moving to relative imports is sensible as our best practice.
There are a few folders we need to do this for - I'm going to split the changes into several separate PRs for my own sanity and to make reviewing (hopefully) easier. I felt like 74 files changed just from replacing imports of core was bulky enough for 1 PR without the other updates too!