Repetitive warning about configuration override

I know this was implemented in response to a previous problem, but the change in https://github.com/DavidAnson/vscode-markdownlint/commit/dd09905d257921094c7c20bacb9ab5869278ffbe. It is giving me a notification that needs to be manually dismissed on every start.

I have checked both user and workspace configurations, and neither contain any settings for markdownlint that are actually overridden. I unfortunately wasn’t able to get the extension set up for development within reasonable time, so I can’t contribute a patch. But I believe a comparison of the loaded config with the default would probably help, something like:

      function loadCustomConfig () {
         var settings = vscode.workspace.getConfiguration(packageJson.displayName);
         customConfig = settings.get("config");
       
         var rootPath = vscode.workspace.rootPath;
         if (rootPath) {
            var configFilePath = path.join(rootPath, configFileName);
            if (fs.existsSync(configFilePath)) {
            isDefaultConfig = customConfig == defaultConfig; // <--- 
               try {
                  customConfig = JSON.parse(fs.readFileSync(configFilePath, "utf8"));
                  if (!isDefaultConfig) { // <----
                      vscode.window.showInformationMessage(configOverride);
               }
               } catch (ex) {
                  vscode.window.showWarningMessage(badConfig + "'" + configFilePath + "' (" + (ex.message || ex.toString()) + ")");
               }
            }
         }

         // Re-lint all open files
         (vscode.workspace.textDocuments || []).forEach(lint);
      }

[DavidAnson]

Yes, thanks, it may have to. I looked at using a status bar message, but that had issues also. My current plan is to suppress the message more aggressively (per above) and then explore your suggestion to display differently.

[DavidAnson]

Update: Switching to a dedicated output window seems to work nicely. I’ll commit and publish soon.