SASS: Programming
2026-02-21 23:41 Diff
https://hexlet.io/courses/sass-programming/lessons/mixin-function/theory_unit

Perhaps the main feature of mixins is that they can accept arguments that we can use internally. Programmers call such portions of code functions. They make it easier to reuse the code. So how do we use this in SASS? Let's take a simple class mx-10 that indents left and right by 10 pixels:

What if we want to add more of these classes? For example, mx-5, mx-10, mx-15, mx-20, and so on. Of course, we can handwrite all the classes we need and set their properties. But this is a boringly long process. Let's first try to put the properties margin-left and margin-right into a mixin so that we don't have to specify them every time:

It seems that not only did nothing much change, but we also added extra code. How does this help us in removing duplicate code? It is where the peculiarity of mixins to accept arguments comes into play.

Arguments are variables on which the result of a function depends. They are given in parentheses and can have any name. We specify each argument with the $ key symbol. If there is more than one argument, they are listed separately by commas.

Let's add two arguments to our mixin. The first argument will point to the value of the margin-right property, and the second argument to the value of the margin-left property:

The second step to turn a simple mixin into a function is to substitute arguments for the properties within the mixin.

To do this, we substitute the arguments we need instead of the values of the properties:

If we try to compile this code now, we get the following error:

The preprocessor tells us that the$mr is missing. It means that once we add arguments to the mixin, we can't call without them, even if we don't use them in the mixin.

Let's correct the error and add two arguments when calling the mixin. We specify the arguments in parentheses and put the value we expect. In this case, it is 10px:

After compiling, we get exactly the code we wanted from the beginning:

The difference now is that we can conveniently write new classes without constantly duplicating properties:

And in this case, since we have repetitive property values, we can pass just one argument and use it in two properties at once:

It is good practice if the properties are related to each other. For example, using the same argument to pass the height and margin-top properties is not a good idea, even if they have the same value. You'll confuse the code and reduce your customization options for the selectors.

The last example showed what happens if you don't specify an argument when you call a mixin. It will not always cause an error because mixins can take arguments by default. If no arguments were specified when calling the mixin, that is what the preprocessor will use.

We specify these arguments directly when we list them and create the mixin. All we have to do is to specify values like a simple variable. It is similar to how the !default' flag was set for a variable:

Since we didn't specify any arguments when calling the mixin, the compiler will take the default value specified when we created the mixin. After compiling, we'll get the following CSS code:

Using the ability of mixins to accept arguments helps a lot when creating property templates with vendor prefixes. In the last lesson, we learned how to make a mixin with the box-shadow property and its vendor prefixes. By using the ability to specify arguments, we can reduce our code when reusing it with other values:

After compiling, we get the following CSS:

Transferring properties in the mixin

In addition to arguments, we can pass the entire CSS code to the mixin. It is useful when, in addition to some values, we need to work with custom CSS, which is absent in the mixin.

You can transfer the content to the mixin as follows:

You can get this content inside the mixin by using the @content construct, which will take the entire body from the mixin call and add it to where the @content construct as specified:

After compiling, we get the following CSS code: