PDA

View Full Version : Why Themer creates save.scss instead of placing variables in proper locations?



maciej.zabielski
2 Jul 2019, 2:24 AM
I don't really like the fact that themer will put custom files like save.scss and throw ALL variables in there in one big unstructured bag.
When I want to modify or change theme manually, I would put the variable in a component specific location, e.g.

If I want to change a header for grid, it should be located in
packages/local/theme-tsl-aria/sass/var/Ext/grid/header/Container.scss

Themer will throw all variables into
packages/local/theme-tsl-aria/sass/save.scss

Whats the point of IDE that produces output that is not in line with general requirements and code structure?

wemerson.januario
29 Aug 2019, 8:43 PM
I don't really like the fact that themer will put custom files like save.scss and throw ALL variables in there in one big unstructured bag.
When I want to modify or change theme manually, I would put the variable in a component specific location, e.g.

If I want to change a header for grid, it should be located in
packages/local/theme-tsl-aria/sass/var/Ext/grid/header/Container.scss

Themer will throw all variables into
packages/local/theme-tsl-aria/sass/save.scss

Whats the point of IDE that produces output that is not in line with general requirements and code structure?


Sencha?