Closed blzaugg closed 6 years ago
We can't use Sass comments for the copyright. It won't be output in the compiled files.
Production output shouldn't need copyright comments, just source code.
@blzaugg I believe production code should contain some sort of copyright info. I think theoretically, it doesn't need it, but depending on what you're bundling, it may very well require it legally.
I think the big issue here is that the copyright is added for every file and not stripped down to only a single one. I believe it's because we stamp each (s)css file in src before compiling it into css. I'm not 100% sure what the best approach for this one would be, since we'd need to handle it both this repo but also in the theme tasks repo as well.
Maybe one option would be to only stamp the top level scss files, and ignore all partials, that way, only the top level generated files that contain everything will have the license, and we wouldn't have to worry about it appearing multiple times.
Just one thought...
Okay, so I guess it's common to have copyright/licence in production code.
I've updated the title/description to focus on the redundancy of the licence comments.
Re-filed together with the rest of licensing issues in the new repo location: https://github.com/liferay/liferay-themes-sdk/issues/48
Expected output:
Actual output: