sass-spec

sass-spec copied to clipboard

See https://github.com/sass/libsass/issues/2841. We should test both raw newlines in strings, which are illegal, and escaped newlines in strings, which are not.

nex3

See https://github.com/sass/sass/issues/2904 - [x] Phase 1 (https://github.com/sass/sass-spec/pull/1608) - [x] Phase 2 (https://github.com/sass/sass-spec/pull/1831) - [ ] Phase 3

nex3

Restructure directories to conform to style guide

9

The directory structure has grown organically over time, and as such does not completely adhere to the recommendations set in the [style guide](https://github.com/sass/sass-spec/blob/master/STYLE_GUIDE.md#do-use-descriptive-paths). For example, some directories have generic names...

Awjin

Add specs for built-in functions

2

All the built-in functions need thorough specs that exercise their edge and error cases. There isn't currently a great structure in place for this; some functions have some specs scattered...

nex3

TS runner interactive mode does not play well with probing todo

1

When running with `--probe-todo --interactive`, the interactive prompt does not allow marking the test as not a todo.

stof

See https://github.com/sass/sass-spec/issues/1516 Adds specs for the value `color`.

Awjin

Refactor `@content` arguments specs

1

jathak

Add stats executable for reporting repo state.

1

Closes https://github.com/sass/sass-spec/issues/1517

Awjin

If the TypeScript runner encounters a failure (at least in non-interactive mode), it just prints "Test case should succeed but it did not". It should also print the failure itself.

nex3

Now that LibSass is deprecated, there's really no use for the `:precision` option in `options.yml`. Dart Sass has never supported it, and we don't expect new implementations to support it.

nex3