CODEWITHSUNDEEP
sasszurb-foundationzurb-foundation-6
yucelm
yucelm

Reputation: 27

Variables in _settings.scss are compiled as uncommented

I have asked this question in Foundation forum but no one has been able to answer yet. Once I run "foundation watch" command, all of the variables inside the src/assets/scss/_settings.sccc file are compiled as uncommented.

On the ZURB website however, it states this:

"To change a setting, find the variable you're looking for, uncomment it by removing the slashes (//) at the start of the line, and change the value. Uncommenting signifies that you want the value to change, and also functions as a handy visual aid to see which defaults you're overriding." - http://foundation.zurb.com/sites/docs/sass.html"

I am really confused as what ZURB website says and what compiler does are totally different from each other. Anyone has any ideas?

Thanks...

Upvotes: 0

Views: 141

Answers (1)

Colin Marshall
Colin Marshall

Reputation: 2142

This was changed after the initial release of Foundation 6. All settings in the settings file now start out as uncommented. The docs just weren't updated yet to reflect the change.

Foundation Developer's Explanation:

The reason we're uncommenting every variable is to avoid reference errors. For example, let's say you left all the colors the same, so they all have comment marks. Now you try to reference $primary-color farther down, and you get an error, because $primary-color hasn't been defined yet. It is in the settings file, but it's not uncommented. Uncommenting every value gets around this issue.

Source: https://github.com/zurb/foundation-sites/issues/7328#issuecomment-161037445

Upvotes: 1

Related Questions