build: fix invalid sass paths being resolved #2169
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.
Prevents SASS from resolving certain paths, even though they're invalid. This should prevent issues like #2133 from happening again.
@jelbourn I'm not sure what the reasoning was for adding
core/styles
to theincludePaths
in Gulp, but this is what helped@import '../a11y/_a11y';
to always be resolved. I re-ran all of the SASS-related Gulp tasks and they went through fine.