Merge pull request #539 from stof/prepare_release

Prepare the 1.10.0 release

docs/_config.yml

@@ -1,6 +1,6 @@
 # Site settings
 title: SCSS Compiler in PHP
-current_version: v1.9.0
+current_version: v1.10.0
 description: >
   SCSS compiler written in PHP
 url: https://scssphp.github.io

docs/docs/changelog.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## **1.10.0** -- January 6, 2022
+
+**Fixed**
+
+* Fix the generation of source maps without an input path (@stof)
+* Fix the handling of list separators in list functions (@stof)
+* Add explicit return types to avoid warnings from the Symfony DebugClassLoader (@shyim)
+
+**Changed**
+
+* Use double quotes to render strings in the generated CSS by default, to match dart-sass (@stof)
+* Remove usage of dynamic properties to avoid deprecation warnings in PHP 8.2-dev (@stof)
+* Change the order of selectors in the output of `selector-append` to match dart-sass (@stof)
+* Mark AST-only types as internal in `\ScssPhp\ScssPhp\Type` (@stof)
+* Preserve the `!` for preserved comments in the compressed output, to match dart-sass (@stof)
+
 ## **1.9.0** -- December 13, 2021
 
 **Added**
@@ -96,7 +112,7 @@
 * Add support for `$blackness` and `$whiteness` in `adjust-color`, `change-color` and `scale-color` (@Cerdic)
 * Add a new `compileString` method returning a `CompilationResult` (@Cerdic, @stof)
 * Add a new `checkImportResolutions` cache option to invalidate the compilation cache if imports would resolve differently (@Cerdic)
-* Add a `LoggerInteface` to customize the handling of warning and debug messages (@stof)
+* Add a `LoggerInterface` to customize the handling of warning and debug messages (@stof)
 * Add the `\ScssPhp\ScssPhp\Warn` API to report warnings in custom functions (@stof)
 * Add `Compiler::replaceVariables` and `Compiler::addVariables` to manage custom variables (@stof)
 * Add the `\ScssPhp\ScssPhp\ValueConverter` to produce values in the Sass value representation (@stof)

docs/docs/extending/custom-functions.md

@@ -47,7 +47,7 @@ There are 3 kinds of arguments that can be declared:
   be the last one.
 
 The compiler will take care of validating arguments against the function
-signature, supporting the same features that for calls to functions defined in
+signature, supporting the same features as for calls to functions defined in
 SCSS directly. However, it is still the responsibility of the callable to
 validate the values themselves. The `Compiler::assert*` helpers should be used
 to validate the type, providing the argument name for better error reporting.
@@ -122,7 +122,7 @@ The direct migration is to declare the function with a rest argument:
  );
 ```
 
-However, in most cases, function actually expect a given signature implicitly
+However, in most cases, functions actually expect a given signature implicitly
 rather than accepting anything. In such case, it is better to migrate to an
 explicit signature and to rework the callable to account for that.
 
@@ -134,4 +134,4 @@ When the error is related to the validation of an argument, the
 `SassScriptException::forArgument` method should be used to instantiate the
 exception.
 
-Warnings can be reported using the `\ScssPhp\ScssPhp\Warn` API:
+Warnings can be reported using the `\ScssPhp\ScssPhp\Warn` API.

src/Version.php

@@ -19,5 +19,5 @@
  */
 class Version
 {
-    const VERSION = '1.9.0';
+    const VERSION = '1.10.0';
 }