To override any scss file user has to duplicate the file and remove the underscore from its name. So for _custom.scss the overriden file would be custom.scss (without _).
This fixes an issue when the user creates an override after the main file has been cached. So if _custom.scss has been compiled and you don't change it but create an override the file is not properly recompiled/refreshed.
It also avoids warnings when a file has been removed after it has been used in a compilation. Let's say that you create a custom.scss file and then your remove it. That caused a php warning. Now it detects that a file has been removed and automatically recompiles the parent file.
To override any scss file user has to duplicate the file and remove the underscore from its name. So for
_custom.scssthe overriden file would becustom.scss(without_).This fixes an issue when the user creates an override after the main file has been cached. So if
_custom.scsshas been compiled and you don't change it but create an override the file is not properly recompiled/refreshed.It also avoids warnings when a file has been removed after it has been used in a compilation. Let's say that you create a
custom.scssfile and then your remove it. That caused a php warning. Now it detects that a file has been removed and automatically recompiles the parent file.