sass-spec
sass-spec copied to clipboard
sass
Official Sass Spec Suite
See https://github.com/sass/sass/issues/3374 - [x] Deprecation - [ ] Removal
See https://github.com/sass/sass/issues/1890 - [x] Deprecation Tests https://github.com/sass/sass-spec/pull/1815 - [ ] Final
See https://github.com/sass/sass/issues/2538 * [x] Deprecation (https://github.com/sass/sass-spec/pull/1807) * [ ] Final
Repro https://github.com/sass/dart-sass/issues/1716 Taking example - https://github.com/KaelWD/sass-forward-twice 1. Removed tab directory and `@forward` rules related to them (same error) 2. Renamed variables in `use module with {...}` to non-existing variables (same...
See https://github.com/sass/sass/issues/3340 * [x] Deprecation * [ ] Removal
The [style guide](https://github.com/sass/sass-spec/blob/main/STYLE_GUIDE.md#dont-have-hrx-files-longer-than-500-lines-or-so) puts a soft 500-line limit on the size of HRX files, but it's currently a fairly onerous manual process to convert a single file into multiple physical...
When using the spec runner's `--interactive` mode, you can select `I` to add implementation-specific outputs that differ from the default behavior of the test. Currently, this adds new outputs of...
See https://github.com/sass/sass/issues/1912, https://github.com/sass/sass/pull/3334 * [x] Test deprecations (https://github.com/sass/sass-spec/pull/1823) * [ ] Test disables
It would be useful to have a CI test that verifies that there aren't any TODO tests associated with closed GitHub issues; once the issues are closed, the TODOs should...
It would be helpful to generate reports on the status of the repo. Some examples of information that would be useful are: * How many specs are marked as TODO...
