Skip to content
This repository was archived by the owner on Oct 24, 2025. It is now read-only.

Conversation

@xzyfer
Copy link
Contributor

@xzyfer xzyfer commented Mar 26, 2016

This patch address two inconsistencies with how @import is
resolved compared to Ruby Sass.

  • .css should not be @importable
  • .sass should take precedence over .scss files

Fixes #1656

This patch address two inconsistencies with how `@import` is
resolved compared to Ruby Sass.
- `.css` should not be `@import`able
- `.sass` should take precedence over `.scss` files

Fixes sass#1656
@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 78.281% when pulling e2422db on xzyfer:fix/import-file-resolution into 213339a on sass:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 78.048% when pulling e2422db on xzyfer:fix/import-file-resolution into 213339a on sass:master.

@mgreter
Copy link
Contributor

mgreter commented Apr 5, 2016

IMO this should wait for 3.4.0 (breaking change) and we should add an opt in config to preserve the current behavior if wanted. We added it because it was widely requested and ruby sass also allows to alter file extensions for including partials. #1893 is also related.

@mgreter mgreter modified the milestones: 3.4, 3.3.5 Apr 6, 2016
@xzyfer
Copy link
Contributor Author

xzyfer commented May 21, 2016

We have decided keeping the current behaviour, and not breaking the code for people who now depending on this, is the lesser evil.

This will be addressed in 4.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add option to control CSS inline import behaviour

3 participants