Sass (scss) files use mixins which are included using @include. If you comment-out an include, you end up with:
// @include foundation-table;
... and preprocess tries to include this as a file.
Some options that I can think of:
Don't match when it contains or ends with a semi-colon.
Technically, a semi-colon is valid in a file name, so this isn't ideal.
Don't match unless it contains a period (.).
A file without an extension is also technically valid, so this is also not ideal.
Use a different syntax, like #include or !include.
This breaks the general pattern of using @, however this may be a good thing, because Sass already has @include syntax, and in fact that is valid in PHP as well.
What do you think? Do we need semi-colons in file paths/names? Do we need files without extensions? Would it make sense to make the @ prefix customizable? Any other ideas?
Sass (scss) files use mixins which are included using
@include. If you comment-out an include, you end up with:... and preprocess tries to include this as a file.
Some options that I can think of:
.).#includeor!include.@, however this may be a good thing, because Sass already has@includesyntax, and in fact that is valid in PHP as well.What do you think? Do we need semi-colons in file paths/names? Do we need files without extensions? Would it make sense to make the
@prefix customizable? Any other ideas?