Instructions for not using $inspect

[mirisuzanne]

Description

Instructions for moving away from $inspect

But I'm having trouble running the build or docs commands…

• build gives me an error about the @import we use for testing legacy support.
• docs gives me a confusing error building the final example in asset/output.scss, insisting that there's a missing {.

[jgerigmeyer]

build gives me an error about the @import we use for testing legacy support.

That's an expected deprecation warning, but doesn't impact the build step.

docs gives me a confusing error building the final example in asset/output.scss, insisting that there's a missing {.

Hm, the Sass playground was reporting the same compilation error -- apparently there was some nonstandard whitespace that was causing an issue. I fixed that, but now there are other True-specific errors on yarn docs:

The `contains-string()` mixin must only be used once per `assert()`

When I remove the second contains-string, then:

Each `assert()` must contain one `output()`, and one `expect()` or `contains()`

[mirisuzanne]

@jgerigmeyer I made it so that multiple contains-string() expectations can be used in a single assertion, but maybe that's wrong. If we like it, we probably need to update the JS as well.

[jgerigmeyer]

@jgerigmeyer I made it so that multiple contains-string() expectations can be used in a single assertion, but maybe that's wrong. If we like it, we probably need to update the JS as well.

@mirisuzanne I'm not sure I understand the tradeoffs (or what JS needs to change) well enough to weigh in.

[mirisuzanne]

@jgerigmeyer test has been added, and fails as expected.

[jgerigmeyer]

@mirisuzanne If this looks good to you, I can make another alpha release.

[mirisuzanne]

@jgerigmeyer looks good. Expand that to contains() and put out another alpha?