Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

!default for scss variables #194

Closed
Ciantic opened this issue Nov 17, 2016 · 7 comments
Closed

!default for scss variables #194

Ciantic opened this issue Nov 17, 2016 · 7 comments

Comments

@Ciantic
Copy link

Ciantic commented Nov 17, 2016

Currently all variables in SCSS are defined using without !default.

In order for them to be overrideable all of them should be defined using !default, see SCSS references

This is related to #123

At least these files should be modified:

https://github.com/palantir/blueprint/blob/master/packages/core/src/common/_font-imports.scss#L7
https://github.com/palantir/blueprint/blob/master/packages/core/src/common/_variables.scss
https://github.com/palantir/blueprint/blob/master/packages/core/src/common/_color-aliases.scss

I'm not sure does this need a default in it:

https://github.com/palantir/blueprint/blob/master/packages/core/src/common/_colors.scss

@dmackerman
Copy link
Contributor

There are also some cases where components aren't consuming variables, for example Button doesn't respect $pt-font-family. I'll see if I can put together a PR will all of these changes.

@adidahiya
Copy link
Contributor

why does Button need to define font-family? Shouldn't it just inherit from base-typography which is applied to body?

@dmackerman
Copy link
Contributor

@adidahiya I found it strange also, but the font didn't change unless I added the variable to @mixin pt-button-base()

@llorca llorca added this to the 1.3.0 milestone Nov 22, 2016
@Reaverart
Copy link

So far I remember, webkit form elements not inherits font-family from body and uses default browser font. font-family: inherit; should fix.

@ugogo
Copy link

ugogo commented Nov 29, 2016

Shouldn't all vars has the !default param?

@giladgray giladgray modified the milestones: 1.3.0, 1.4.0 Dec 5, 2016
@dmackerman
Copy link
Contributor

So now that the ~ import syntax is supported, this seems like something I could take a crack at doing now.

@giladgray
Copy link
Contributor

certainly crack-worthy, i'd wager 🎩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants