Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a improvement.
As bulma colors are kind hard-coded into a map, which wrap colors and functions (findColorInvert), to extend them you have to import variables and functions then customize your style, then import derived variables and reassing colors to a merged map. Damn this is heavy. I've come to solution where you set you customizations to $custom-colors variable, the way bulma does, and then you import bulma, done.
Proposed solution
Add a function in
utilities/functions.sass
that handle$custom-colors
to merge it with bulma's$colors
droping malformated elements. Assing it to$colors
inutilities/derived-variables.sass
so it can be overriden and is backward compatible with 'old' integrations.Tradeoffs
Can't see anyone... 1 call over whole project, with relatively small maps
Testing Done
Customized through
$custom-colors
with malformated elements, then compiled and used in html page. All custom (proper) and base colors where accessible with.is-#{name}
classes dependent of colors.