Cannot disable minifier and gzip with configuration file

[rwasef1830]

Hello, For some reason even though my config file looks like this:

{
  "Minifiers": {
    "GZip": false,
    "Enabled": false
  },
  "CompilerSettings": {
    "Sass": {
      "IndentType": "Space",
      "IndentWidth": 2,
      "OutputStyle": "Nested",
      "Precision": 5,
      "RelativeUrls": true,
      "LineFeed": "Lf",
      "SourceMap": true
    }
  },
  "Output": {
    "Preserve": true
  }
}

And I run webcompiler tool like this:

dotnet watch tool run webcompiler -r wwwroot 

With the current directory being the project directory that contains webcompilerconfiguration.json It still minifies and gzips the js and css. Basically ignoring the config file. It does this even when I explicitly pass -c webcompilerconfiguration.json

Am I missing something ?

[rwasef1830]

It seems webcompilerconfguration.json is not searched in the current directory the tool is called from, but instead in the directory passed to -r. This seems to be a regression, or was it the intended behavior ? At least the documentation needs to clarify this point.

[stefanloerwald]

Hi @rwasef1830,

I've started investigating the issue you're experiencing. Here's what I can say so far:

• Omitting the config option will not work. This tool does not look for a config file unless explicitly specified, so the expected behavior in this case is to have the minification.

• However, explicitly passing the configuration file should work. In the tests I've wrote (see commit https://github.com/excubo-ag/WebCompiler/commit/2eca76fe4dfaf231fc8b4a221e68d65a94074783), the behavior seems fine, i.e. the config file is correctly read. -r shouldn't be able to mess with that, as this option is only handled at a later point in time.

Could you please show the exact command line parameters you're using, and perhaps the directory structure? Thanks!

[rwasef1830]

Retesting this, you're correct, I was getting confused by a mixture of 2 things in addition to late night.

1. I accidentally had dotnet watch tool running in another desktop that was interfering with my tests that I couldn't see.
2. Rider was delayed in updating the directory structure so what I was seeing wasn't immediately reflecting the latest directory structure.

• It is working correct, and the config is read from current dir not -r dir.

My apologies, this bug report is invalid.

[stefanloerwald]

Thank you for the quick feedback, and no worries: having those two additional tests might just prevent a regression in some future version, so it's a good thing to have it covered. Thanks!