in-place compilation about aspnetcore.sasscompiler HOT 5 CLOSED

Hi @patricksadowski , I totally get what you mean. But it's actually optional to use the input and output folders as you can also make use of the ScopedCssFolders and set GenerateScopedCss to true. Let me know if this solves your problem

from aspnetcore.sasscompiler.

My current sasscompiler.json contains

{
    "Arguments": "--no-source-map --style=compressed",
    "ScopedCssFolders": ["."]
}

and it's working. So, the thanks are yours.

Now, I have to copy the configuration to several projects in the same repo. I would like to place the configuration once in root. That would be a great feature: use the configuration up in the directory tree. Even better would be a "install and forget" package for a simple sass compilation use case without configuration 😉

from aspnetcore.sasscompiler.

Shall I file new issues for the mentioned features or does this issue care for the new feature requests?

from aspnetcore.sasscompiler.

@patricksadowski We have an install and forget option as it already uses the defaults. But the default looks in the /Styles folder and compiles the files to the wwwroot/css folder. I think this is the most common use case. Do you agree? I understand that using the ScopedCssFolders wildcard is very useful for your project but may cause unwanted files to be generated for other users. Please tell me if I overlook something here.

from aspnetcore.sasscompiler.

@koenvzeijl I agree. We changed some points in our repo so your package fits better.

from aspnetcore.sasscompiler.