I want to have a map of all bootstrap vars i'm using in sass.
$FULL_MAP = ("bootstrap": #include(bootstrap/_variables.scss)
To achieve this, do I have to manually rewrite the whole file?
I have ended up manually putting required vars into a map and then using themify mixing in order to apply vars from the map. The code is on github and this is the file that puts variables into the map
.custom-scope {
#import "~bootswatch/dist/cerulean/variables";
$cerulean: (
"primary":$primary,
"secondary":$secondary,
"success":$success,
"info":$info,
"warning":$warning,
"danger":$danger,
"light":$light,
"dark":$dark
);
$themes: map_merge($themes, ("cerulean": $cerulean)) !global;
}
Related
I want to get data attr which is a number from HTML in my scss file and do a for loop on elements.
so here's what i did :
HTML :
<figure class="inner" data-attr="8"></figure>
SCSS
[data-attr] {
$no: attr('data-attr') !global;
}
and
#for $i from 0 through $no {
&:nth-of-type(#{$i}) {
left: $no;
}
}
but I got an error :
Error: attr("data-attr") is not an integer.$no: attr('data-attr') !global
You'll need to take a different approach.
SASS is a pre-processor that compiles into a CSS file. You can't use a SASS loop to generate CSS output based on a value that you don't have at the time of compilation.
Without knowing what you're actually attempting to do, it's not possible to suggest an alternative solution either.
I have some Sass variables that I want to deprecate soon. How do I do it, without changing the implementation of it?
I want to allow the usage of variables below, but I want to show a message during the compilation step (whenever they are used), that the variables below are going to be deprecated. Is it possible? Also, can I display where the deprecated variable was used?
$screen-xs-min: 320px;
$screen-sm-min: 480px;
$screen-md-min: 768px;
$screen-lg-min: 992px;
$screen-xl-min: 1200px;
$screen-xs-max: ($screen-sm-min - 1);
$screen-sm-max: ($screen-md-min - 1);
$screen-md-max: ($screen-lg-min - 1);
$screen-lg-max: ($screen-xl-min - 1);
I was looking for the solution for this as well and created my own. Maybe this will help someone else.
#use "sass:list";
// The key is the deprecated variable, note the missing $. The value is the newly suggested one.
$deprecated: (
"font-size-h1": "$font-size-h1-clamp",
"font-size-h2": "$font-size-h2-clamp",
"font-size-h3": "$font-size-h3-clamp",
"font-size-h4": "$font-size-h4-clamp",
"font-size-medium": "$font-size-medium-clamp",
"font-size-large": "$font-size-large-clamp",
"font-size-extra-large": "$font-size-extra-large-clamp",
);
#each $variable in $deprecated {
#if variable-exists(list.nth($variable,1)) {
#warn "The scss variable $#{list.nth($variable,1)} is deprecated. Please use #{list.nth($variable,2)} instead.";
}
}
I've inherited a project and it has a variable list/map in its scss file, which has:
$palette: (
success: #53a646,
warning: #faa41a,
alert: #ec5840,
);
I want to use one of these variables (warning) and apply it to an element. I've googled but have not been able to find a way to apply it.
I've seen examples like:
.warning-btn {
background-color: nth($palette, 2);
}
But this isn't working for me.
Would anyone know the correct way of applying the variable to an element?
change your code to the following
$palette: (
success: #53a646,
warning: #faa41a,
alert: #ec5840,
);
.warning-btn {
background-color:#{map-get($palette,warning)}
}
Hope it helps
How can I pass the return value form a custom Sass function to a Susy function?
Or is there any better approach?
This works fine:
.foo{
max-width: get_breakpoint('large');
}
But that won't:
.foo{
#include layout(get_breakpoint('large') 12);
}
Susy just falls back to the default container width instead of using the one from my get_breakpoint() function.
The built uses Compass, I have the following function in my config.rb:
module Sass::Script::Functions
#
# get breakpoint values from prefs file (json)
#
def get_breakpoint(bp)
if PROJ_PREFS['breakpoint'].include?(bp.value)
retVal = PROJ_PREFS['breakpoint'][bp.value][0].to_s+'px'
else
retVal = bp.to_s
end
Sass::Script::String.new(retVal)
end
end
Software versions: sass (3.4.21), compass (1.0.3), susy (2.2.12).
Many thanks.
It turns out that it shouldn't be a problem to use a custom function as a Susy mixin argument as long as it passes the right value. I was passing a string instead of Sass number.
Just in case someone stumble across similar problem, below there is an example of working solution retrieving breakpoint values from Json into Sass (Assuming you've got json gem installed).
Note that this solution isn't perfect from the performance point of view as it recreates the $BREAKPOINT map each time the _base.scss partial is imported. (It also omits my custom breakpoint mixin as not relevant here and which uses the breakpoint function as well)
My breakpoint definitions are stored as 'unitless' numbers in json
{
"breakpoint" : {
"mini" : [ 481 , "phablet portrait phone landscape"],
"xsmall" : [ 736 , "phablet landscape (iPhone6plus) tablet portrait"],
...
Ruby code (in Compass config.rb)
require 'json'
file = File.read(File.dirname(__FILE__)+'/preferences.json')
PROJ_PREFS = JSON.parse(file)
module Sass::Script::Functions
def get_breakpoints()
retMap = Hash.new
PROJ_PREFS['breakpoint'].each do |bp_name, bp_value|
retMap[Sass::Script::Value::String.new(bp_name.to_s)] = Sass::Script::Value::Number.new(bp_value[0],'px')
end
Sass::Script::Value::Map.new(retMap)
end
end
Sass code (e.g. _base.scss)
// create Sass map with custom function
$BREAKPOINT:get_breakpoints();
// allow Sass numbers (such as 12em, 355px) or breakpoint names (such as small, large) to be passed through
// it was just easier for me to code it in Sass (since I don't know Ruby at all)
#function breakpoint($key) {
#if not map-has-key($BREAKPOINT, $key) { #return $key; }
#return map-get($BREAKPOINT, $key);
}
Usage example (involving Susy)
.foo{
#include container(breakpoint(large));
}
AS the title says I am trying to check whether a variable is defined in SASS. (I am using compass if that makes any different difference)
I've found the Ruby equivalent which is:
defined? foo
Gave that a shot in the dark but it just gave me the error:
defined": expected "{", was "?
I've found a work around (which is obviously just to define the variable in all cases, which in this case it actually makes more sense) but I'd really like to know if this is possible for the future
For Sass 3.3 and later
As of Sass 3.3 there is a variable-exists() function. From the changelog:
It is now possible to determine the existence of different Sass constructs using these new functions:
variable-exists($name) checks if a variable resolves in the current scope.
global-variable-exists($name) checks if a global variable of the given name exists.
...
Example usage:
$some_variable: 5;
#if variable-exists(some_variable) {
/* I get output to the CSS file */
}
#if variable-exists(nonexistent_variable) {
/* But I don't */
}
For Sass 3.2.x and earlier (my original answer)
I ran into the same problem today: trying to check if a variable is set, and if so adding a style, using a mixin, etc.
After reading that an isset() function isn't going to be added to sass, I found a simple workaround using the !default keyword:
#mixin my_mixin() {
// Set the variable to false only if it's not already set.
$base-color: false !default;
// Check the guaranteed-existing variable. If it didn't exist
// before calling this mixin/function/whatever, this will
// return false.
#if $base-color {
color: $base-color;
}
}
If false is a valid value for your variable, you can use:
#mixin my_mixin() {
$base-color: null !default;
#if $base-color != null {
color: $base-color;
}
}
If you're looking for the inverse, it's
#if not variable-exists(varname)
To check if it is undefined or falsy:
#if not variable-exists(varname) or not $varname
And if you want to set it only if it's undefined or null
$varname: VALUE !default;
Just as a complementary answer - you should have a look on the default keyword for certain use cases. It gives you the possibility to assign a default value to variables in case they are not defined yet.
You can assign to variables if they aren’t already assigned by adding
the !default flag to the end of the value. This means that if the
variable has already been assigned to, it won’t be re-assigned, but if
it doesn’t have a value yet, it will be given one.
Example:
In specific-variables.scss you have:
$brand: "My Awesome Brand";
In default-variables.scss you have:
$brand: company-name !default;
$brand-color: #0074BE !default;
Your project is built like this:
#import "specific-variables.scss";
#import "default-variables.scss";
#import "style.scss";
The value of brand will be My Awesome Brand and the value of brand color will be #0074BE.