Christophe Coevoet
Christophe Coevoet
Once #424 is complete, implementing the indented syntax won't be a lot of work (I kept the separation between `StylesheetParser` and `ScssParser` on purpose to make it possible to port...
Currently, our SassSpecTest is always asserting the default `warning`, not considering alternative `warning-dart-sass`. This is not consistent with our handling of the output. Currently, libsass renders warning without any location...
After staring my work on #265, I realised that merging that work into 1.x is too risky regarding backward compatibility, due to #201. The existing array-based value API is less...
## Motivation Currently, the `Compiler` class is huge (approx 9kLOC) which makes it harder to work on them: - identifying the public API is hard - such big file slows...
libsass is being deprecated according to https://github.com/sass/libsass/issues/3123, because they don't have the resources to keep it uptodate with the sass language. For now, Scssphp is less compliant than libsass AFAICT,...
The library currently implements a `Cache` that can be used to speed up the compilation. But that implementation is quite limited as it forces a filesystem-based cache. I suggest providing...
As part of the on-going effort to become spec-compliant and to make it easier to implement modern sass features in the future, I'm convinced we need to modernize the architecture...
#214 reports than Gantry 5 overrides the importer-related methods to use their `gantry-theme` stream wrapper to resolve file. We should look at a way to support such use case through...
Currently, we rely on the sass-spec convention of separating tests with a delimiter comment to identify the different specs. This causes issues when the convention is not properly respected (see...