Depreciation warning for colors
See original GitHub issueHi, I actually just have a usage question, but I can’t find anywhere to ask it. I couldn’t find a link to any forum, mailing list or chat from your repo, homepage or docs.
I would like to know how to get rid this depreciation warning:
DEPRECATION WARNING on line 145, column 67 of /.../layout.scss:
The value "#AAAAAA00" is currently parsed as a string, but it will be parsed as a color in
future versions of Sass. Use "unquote('#AAAAAA00')" to continue parsing it as a string.
What should I do? I DON’T want it parsed as a string - it’s a color.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Depreciation warning for colors in Angular - Stack Overflow
The value "#c6c6c636" is currently parsed as a string, but it will be parsed as a color in future versions of Sass.
Read more >The operation `color plus 33` is deprecated and will be an ...
The operation `color plus 33` is deprecated and will be an error in future versions. in dart-sass. DEPRECATION WARNING on line 101 of...
Read more >warnings — Warning control — Python 3.11.1 documentation
Base category for warnings about deprecated features when those warnings are intended for other Python developers (ignored by default, unless triggered by ...
Read more >Gulp throws deprecation warnings coming from init/_colors ...
Gulp produces a lot of SASS 4.0 deprecation warnings coming from the _colors.scss file. These are caused by the node_module/chroma_sass ...
Read more >Breaking Change: Color Units | Sass 中文网
Finally, we'll remove all deprecated behavior by making color functions throw errors if they're passed any units that produced deprecation warnings in Phase ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The value
#AAAAAA
will work just fine. It’s only the syntax#AAAAAA00
, which represents opacity as hex digits, which isn’t supported yet and requires the use of thergba()
function right now.@nicolasxu-bg That syntax isn’t supported yet in some Sass implementations. Use the
rgba()
function instead.