Sass

Sass

The sass object declares the paths to each application entry point and all Sass files to be loaded when you deploy. You should manually add any new Sass files to the files array that you introduce as part of your theme customizations.

Note:

When listing a new Sass file, declare each file in an order that makes the most semantic sense within the Sass hierarchy.

json

1//...
2"sass": {
3   "entry_points":{ 
4      "shopping":"Modules/Shopping/shopping.scss",
5      "myaccount": "Modules/MyAccount/myaccount.scss",
6      "checkout": "Modules/Checkout/checkout.scss"
7   }
8   "files":[ 
9      "Modules/Shopping/shopping.scss",
10      "Modules/MyAccount/myaccount.scss",
11      "Modules/Checkout/checkout.scss",
12      "Modules/twitter-bootstrap-sass@3.3.1/assets/stylesheets/bootstrap/_alerts.scss",
13      //...
14   ]
15}
16//...

Frequently Asked Questions (4)

How should I order new Sass files in the 'files' array?

New Sass files should be declared in an order that makes semantic sense within the Sass hierarchy to maintain logical structure and dependencies.

Do I automatically need to update the 'sass' object when deploying new themes?

Yes, you should manually add any new Sass files to the 'files' array within the 'sass' object as part of your theme customizations when deploying.

What happens if I omit a new Sass file from the 'files' array?

The new Sass file will not be loaded with the application, which could result in missing styles or incorrect theme application.

Is it necessary to specify application entry points in the 'entry_points' object?

Yes, each application entry point like 'shopping', 'myaccount', etc., should be declared in the 'entry_points' object to ensure the correct loading of Sass files for each module.

Frequently Asked Questions (4)

More in General