Opened 10 years ago
Closed 7 years ago
#15347 closed enhancement (wontfix)
Add support to builds to process .less @imports
Reported by: | Chris Mitchell | Owned by: | Rawld Gill |
---|---|---|---|
Priority: | low | Milestone: | 1.11 |
Component: | BuildSystem | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
When using .less and dynamic changes to colors/fonts, it would be nice to have aggregated .less files for themes similar to how cssImports are handled during the build step.
Change History (3)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Milestone: | tbd → 2.0 |
---|---|
Priority: | undecided → low |
Status: | new → assigned |
@chrism:
I'm happy to explore more integration of less into the builder. However, a couple of weeks back we had a big debate about whether or not we are going to continue using less. Also, I'm not exactly sure what you're asking for. For those two reasons, I'm punting this to 2.0
comment:3 Changed 7 years ago by
Milestone: | 2.0 → 1.11 |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
I think this would be better handled in the future by relying on the CSS preprocessor, rather than having the build system become a preprocessor.
Note: See
TracTickets for help on using
tickets.
I don't understand what this ticket means. Are you talking about downloading the less files to the client and then converting them to CSS on the client? Since you are doing a build anyway, why not convert less to CSS on the server?
You mentioned "dynamic changes to colors/fonts" as though that requires less, but actually people have been dynamically changing colors and fonts long before less existed.