Offering different versions of Compass extensions

[lolmaus]

Some Compass extensions have incompatible syntax changes between versions.

For example, all existing Singularity gists will break when you update Singularity to the 1.2.0 version which has been released recently.

There's only one way to resolve this issue: allow for importing different extension versions just like you allow different versions of Sass.

[rpkoller]

+1 would be an handy and useful addition

[jedfoster]

Sorry, this just isn't doable.

[lolmaus]

That's very sad.

As i said, all Singularity gists will break once you update Singularity to 1.2.0. :(

[jedfoster]

You could ask the maintainers of that library to fix it's backward-compatibility.

[lolmaus]

That's not going to happen, they have made a lot of changes to the API.

Backward-incompatible changes do happen, we can't expect that Compass extensions will never deprecate stuff.

Can you at least maintain two sets of extensions: one for Sass 3.2 and one for Sass 3.3?

[Snugug]

For the record, this isn't an issue that's constrained to Singularity's recent upgrade (which was needed due to changes in how Sass 3.3 handles variables and conflicts with Compass itself), this will be an issue with any extension that goes through any form of major upgrade. Toolkit just got a 2.0.0 release which is backwards incompatible with its 1.0.0 version, which means all code relying on Toolkit 1.0.0 will break. Susy is getting a serious upgrade too.

SassMeister is a tool for playing with the most up-to-date versions of various Sass extensions, not a replacement for Sass itself.

Finally, any issues with Singularity should probably be posted in the Singularity issue queue, not the SassMeister one.

[jedfoster]

Yes. The Sass 3.2 compiler on SassMeister will remain, for the foreseeable future, along with its compatible extensions—at least until Sass 3.4 beta lands.

[lolmaus]

@jedfoster So you can upgrade Singularity, Toolkit (and probably other extensions that rely on new Sass features) only for the Sass 3.3 mode and leave their previous versions for the Sass 3.2 mode?

[Snugug]

@lolmaus If you had taken a look at the extension versions for Sass 3.2, you would have seen that already is the case.

[lolmaus]

Awesome!