Open mbolli opened 4 months ago
It's a fair criticism. The new system is supposed to leverage the flexibility of the HSL color format to easily customize your components.
I think some component like the Menu or the Pagination could do without this sytem. I'll see what I can do.
I've had a similar experience migrating my projects – it was managable, but coupled with the paradigm shift SASS namespacing forced on the styles quite complicated and error-prone.
Regarding simplifying some component's colors: at least for me, that unfortunately wouldn't solve the underlying problem.
Right now I have a need to set button color variants to exact foreground-background pairs that were defined by a designer, this seems to only be possible by enumerating the colors and restyling .button.is-*
classes… That's quite the step backwards from 0.x and seems to be something that should be easily achievable in the new theming system.
A minimal change that could help: if the hsla-calculations were stored in sass-variables (or even just separate css-vars) they could be overriden as regular colors.
I've come across some similar difficulty when trying to upgrade the checkradio plugin. It appears abandoned so I'm just going to internalise it. They did things like this:
@each $name, $pair in $colors
$color: nth($pair, 1)
$color-invert: nth($pair, 2)
But now there's no guaranteed inverted colour. Is there a simple way to get a list of colours and their inverts in the rewrite? Looking at the code for button
, the colours look very complicated now :)
I went for this approach in the end:
@use "sass:list"
@use "bulma/sass" as bulma
@use "bulma/sass/utilities/functions"
@each $name, $pair in bulma.$colors
$color: list.nth($pair, 1)
$color-invert: functions.bulmaFindColorInvert($color)
@if list.length($pair) > 1
$color-invert: list.nth($pair, 2)
This is about Bulma v1 and the needed migration - not a bug.
Overview of the problem
This is about the Bulma CSS framework I'm using Bulma 1.0.2 My browser is: latest Chrome I am sure this issue is not a duplicate
Description
This is how I modified Bulma to project requirements in 0.9.4:
Essentially I was just able to go into the sass file, e.g.
menu.sass
, see what variables are available, e.g.and go from there.
Now when trying to migrate to v1:
Obviously it doesn't work, as most of the variables are not there anymore. So I go into
menu.scss
:How would I go about setting
$menu-item-active-color: #fff; $menu-item-active-background-color: transparent
? The:hover
and:active
styles only override the background luminance delta.Do I need to go back to override like this?
I mean, the upper way (variant 1) would be easy enough, but feels somehow wrong. And there's a big chance to miss something. The lower way (variant 2) is just really verbose and it doesn't look like everything's overridable. And there's the same chance to miss something.