components: Some SCSS files refer to invalid path (a11y)
In 5cf7d175d66120b0e8262bef561f230cb6e31d11 several components got a11y support using a new SCSS resource.
The import is @import '../a11y/_a11y';
Which looks for the file in material/src/lib/a11y/_a11y
a11y is in core
The file exists in material/src/lib/core/a11y/_a11y
I don’t know how the build passed but it’s should be fixed
@import '../core/a11y/_a11y';
The files: src/lib/button/button.scss src/lib/card/card.scss src/lib/dialog/dialog-container.scss src/lib/menu/menu.scss src/lib/select/select.scss src/lib/sidenav/sidenav.scss src/lib/slide-toggle/slide-toggle.scss src/lib/snack-bar/snack-bar-container.scss src/lib/tooltip/tooltip.scss
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 15 (14 by maintainers)
Commits related to this issue
- build: fix wrong SASS path Fixes SASS errors when Material is imported directly. Fixes #2133. — committed to crisbeto/material2 by deleted user 8 years ago
- build: fix wrong SASS paths Fixes SASS errors when Material is imported directly. Fixes #2133. — committed to crisbeto/material2 by crisbeto 8 years ago
- build: fix wrong SASS paths (#2135) Fixes SASS errors when Material is imported directly. Fixes #2133. — committed to angular/components by crisbeto 8 years ago
- build: fix invalid sass paths being resolved Prevents SASS from resolving certain paths, even though they're invalid. This should prevent issues like #2133 from happening again. — committed to crisbeto/material2 by crisbeto 8 years ago
- build: fix invalid sass paths being resolved (#2169) Prevents SASS from resolving certain paths, even though they're invalid. This should prevent issues like #2133 from happening again. — committed to angular/components by crisbeto 8 years ago
alpha.11-3 is released, should fix this
Oh, I see. Yeah no idea how that ended up compiling. I’ll put in a PR.