https://alcops.dev/docs/analyzers/common/Recent content in Common on ALCopsHugoen-ushttps://alcops.dev/docs/analyzers/common/cm0001/Mon, 01 Jan 0001 00:00:00 +0000https://alcops.dev/docs/analyzers/common/cm0001/<p><code>CM0001</code> warns when an <a href="https://alcops.dev/docs/getting-started/configuration/"><code>alcops.json</code></a> configuration file was found but could not be fully applied. Without this warning a broken configuration silently falls back to the default settings, and it can be hard to understand why your settings have no effect.</p> <p>The message names the file and the reason:</p> <pre tabindex="0"><code>The ALCops configuration &#39;C:\Source\MyApp\alcops.json&#39; could not be fully loaded: unknown setting &#39;CognitivComplexityThreshold&#39; </code></pre><h3 id="when-it-is-reported">When it is reported</h3> <table> <thead> <tr> <th>Situation</th> <th>Effect on settings</th> </tr> </thead> <tbody> <tr> <td>The file exists but cannot be read (I/O or permission error)</td> <td>Defaults are used</td> </tr> <tr> <td>The file contains invalid JSON (syntax error, wrong value type, unknown enum value)</td> <td>Defaults are used</td> </tr> <tr> <td>The file is valid JSON but contains an unrecognized top-level setting (for example a typo in the name)</td> <td>All recognized settings still apply; one warning per unknown setting</td> </tr> </tbody> </table> <p>No warning is reported when no <code>alcops.json</code> exists — using the defaults without a configuration file is perfectly fine.</p>