Skip to content

Commit d7cf8e0

Browse files
Update CHANGELOG entry
Highlight that despite remaining available, although deprecated, Sass variables now store a different type of data, which will break existing computations. Co-authored-by: seaemsi <[email protected]>
1 parent eea87fb commit d7cf8e0

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

CHANGELOG.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,9 @@ If you were using the value of one of the variables in [`settings/_colours-appli
3939
| `$govuk-link-hover-colour` | `govuk-functional-colour(link-hover)` |
4040
| `$govuk-link-active-colour` | `govuk-functional-colour(link-active)` |
4141

42+
Although we've now deprecated the Sass variables, they're still available to make your migration easier.
43+
However, if your code was using the Sass variables to do computations using the [Sass colour API](https://sass-lang.com/documentation/modules/color/), a compilation error will occur. This is because the variables now store a Sass string with a `var()` call, rather than a Sass colour.
44+
4245
#### Use `$govuk-functional-colours` to redefine functional (formerly applied) colours
4346

4447
We've restructured our applied colours in Sass. They are now called functional colours, and we've changed the way you redefine them.

0 commit comments

Comments
 (0)