CodeKit2

CodeKit2 copied to clipboard

Having this issue. Not sure since when this occurs.

`Compiled successfully, but Compass issued these warnings:

DEPRECATION WARNING on line 87 of /Applications/CodeKit.app/Contents/Resources/engines/compass/compass-core/stylesheets/compass/css3/_deprecated-support.scss: #{} interpolation near operators will be simplified in a future version of Sass. To preserve the current behavior, use quotes:

unquote('"$moz-"#{$experimental-support-for-mozilla} "$webkit-"#{$experimental-support-for-webkit} "$opera-"#{$experimental-support-for-opera} "$microsoft-"#{$experimental-support-for-microsoft} "$khtml-"#{$experimental-support-for-khtml}')

You can use the sass-convert command to automatically fix most cases.

DEPRECATION WARNING on line 92 of /Applications/CodeKit.app/Contents/Resources/engines/compass/compass-core/stylesheets/compass/css3/_deprecated-support.scss: #{} interpolation near operators will be simplified in a future version of Sass. To preserve the current behavior, use quotes:

unquote('"$ie6-"#{$legacy-support-for-ie6} "$ie7-"#{$legacy-support-for-ie7} "$ie8-"#{$legacy-support-for-ie8}')

You can use the sass-convert command to automatically fix most cases.`

Are you sure this is CodeKit's issue? It seems like its giving you the answer in the output. Either way, it seems like a syntax error more than anything else.

Compass needs to update to support the newer Sass syntax released in CodeKit 2.7.1. When they do, I’ll update CodeKit to include that newer version of Compass. In the meantime, I’d consider migrating away from Compass because doing so will let you compile your Sass files with Libsass, which will change your life. Check out Bourbon for a possible replacement.

On 22 Feb 2016, at 04:18, Hobbit78 [email protected] wrote:

Having this issue. Not sure since when this occurs.

`Compiled successfully, but Compass issued these warnings:

DEPRECATION WARNING on line 87 of /Applications/CodeKit.app/Contents/Resources/engines/compass/compass-core/stylesheets/compass/css3/_deprecated-support.scss: #{} interpolation near operators will be simplified in a future version of Sass. To preserve the current behavior, use quotes:

unquote('"$moz-"#{$experimental-support-for-mozilla} "$webkit-"#{$experimental-support-for-webkit} "$opera-"#{$experimental-support-for-opera} "$microsoft-"#{$experimental-support-for-microsoft} "$khtml-"#{$experimental-support-for-khtml}')

You can use the sass-convert command to automatically fix most cases.

DEPRECATION WARNING on line 92 of /Applications/CodeKit.app/Contents/Resources/engines/compass/compass-core/stylesheets/compass/css3/_deprecated-support.scss: #{} interpolation near operators will be simplified in a future version of Sass. To preserve the current behavior, use quotes:

unquote('"$ie6-"#{$legacy-support-for-ie6} "$ie7-"#{$legacy-support-for-ie7} "$ie8-"#{$legacy-support-for-ie8}')

You can use the sass-convert command to automatically fix most cases.`

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/606.

same issue here. is there a way to downgrade codekit ?

You don't want to downgrade. You can safely ignore the warning until compass is updated.

Sent from my iPhone

On Mar 2, 2016, at 06:42, fauckenthaler [email protected] wrote:

same issue here. is there a way to downgrade codekit ?

— Reply to this email directly or view it on GitHub.

except that for me it wasnt a warning. it wasnt able to compile my scss file. it looked more like an error.

In that case, it wasn’t the same issue. Deprecation warnings do not prevent compiling. And either way, I recommend migrating away from Compass so that you can compile with Libsass. Libsass is the official future of Sass; you’ll have to migrate someday because the Ruby Sass compiler is eventually going to become a wrapper around Libsass and Compass does not support Libsass.

On 2Mar 2016, at 14:51, fauckenthaler [email protected] wrote:

except that for me it wasnt a warning. it wasnt able to compile my scss file. it looked more like an error.

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/606#issuecomment-191479407.

how to fix issue T_T please

Same issue here. Is there a fix that doesn't involve switching to Bourbon?

Not currently. But I recommend the switch anyway because then you'll be able to compile with Libsass, which will change your life.

I have no issue switching to Libsass etc, but is there a guide how to do it? does that work from an existing project or would i have to start fresh?

Well, it depends on what you’re using. Bourbon is just a bunch of mixins, so you would replace the calls to Compass’s mixins with calls to Bourbon’s instead. If you’re still relying on Compass for vender prefixes, you would get rid of that and simply enable AutoPrefixer in CodeKit.

On 11Mar 2016, at 04:32, fauckenthaler [email protected] wrote:

I have no issue switching to Libsass etc, but is there a guide how to do it? does that work from an existing project or would i have to start fresh?

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/606#issuecomment-195349175.

What would recommend for working with Magento 1.9? It specifically uses Compass. I tried switching to Bourbon, but I'm getting stuck on several missing mixins.

Thanks!

I don’t have a specific recommendation, as I’ve never worked with Magento. The warnings aren’t errors, however, and can be ignored for now.

On 14Mar 2016, at 12:00, JonnaIsaac01 [email protected] wrote:

What would recommend for working with Magento 1.9? It specifically uses Compass http://devdocs.magento.com/guides/m1x/ce19-ee114/RWD_dev-guide.html#compass-install. I tried switching to Bourbon, but I'm getting stuck on several missing mixins.

Thanks!

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/606#issuecomment-196474160.

It is breaking the site, and I'm seeing this error:

Error: no mixin named opacity

       Backtrace:
        ...
>>         @include opacity(0.8);

How would I fix this to be compatible with Bourbon?

Thanks!

You wouldn’t use an opacity mixin any longer. You would write standard, modern CSS and allow AutoPrefixer to transform that CSS into rules that apply to the browsers you specify in the AutoPrefixer browser string. Opacity has long been standardized on modern browsers at this point.

On 14Mar 2016, at 12:06, JonnaIsaac01 [email protected] wrote:

It is breaking the site, and I'm seeing this error: Error: no mixin named opacity

Backtrace: ... @include opacity(0.8); How would I fix this to be compatible with Bourbon?

Thanks!

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/606#issuecomment-196477066.

I went through and updated all the mixins that Codekit showed errors for (replacing the mixins with standard CSS). Took less than 15 minutes and now my Magento site is running smoothly with Bourbon instead of Compass. Thanks for your help and patience!

I'm using Bourbon, and I still get this warning.

DEPRECATION WARNING on line 37 of /Users/[username]/Applications/CodeKit.app/Contents/Resources/engines/bourbon/css3/_radial-gradient.scss: #{} interpolation near operators will be simplified
in a future version of Sass. To preserve the current behavior, use quotes:

  unquote("#{$pos}#{$shape-size}#{$full}")

I totally understand these warnings, but could they be handled by CodeKit differently? A checkbox for "Silently log deprecation warnings", for example? The command line ruby warns on the first compile and is then silent on subsequent compiles during that session. Libsass is the future and I will jump on soon enough, but, for now, I just want to give the kids lollipops until we get to Grandma's.

Those checkboxes exist in the app's preferences window.

It does not pop to the front which is great, but the notification still comes up as success with warnings.

I don't mean to be a nitpicker. I love this app and it has saved me since needing to upgrade to El Capitan.

I am, however, able to turn off these notifications in the Notification Center for OS X. I also added a line to the config.rb to play a sound on successful save. I am happy.