Open martindevans opened 9 years ago
I'm not sure.
Not convinced that having some custom way to define stuff to build files which then build more files is the way to go.
I'll have a think about a solution On 12 Mar 2015 12:03, "Martin Evans" notifications@github.com wrote:
There is a less config file (lcars-variables.less), now that ts is dynamically generating some of the style we also need the same values in a ts config file.
What's the best way to only have to configure this once? Perhaps have a yaml file with config values which we parse as part of the gulp process and spit out intermediate .less and .ts files for the rest of the build?
— Reply to this email directly or view it on GitHub https://github.com/martindevans/LCARS/issues/42.
Weren't we always going to provide a build process anyway? Changing the config file requires that you rebuild all the less files, so it kinda sucks if we just throw less at the user and say "build this".
There is a less config file (lcars-variables.less), now that ts is dynamically generating some of the style we also need the same values in a ts config file.
What's the best way to only have to configure this once? Perhaps have a yaml file with config values which we parse as part of the gulp process and spit out intermediate .less and .ts files for the rest of the build?