Closed PythonCoderAS closed 5 months ago
It sounds like your project or your configuration are referencing an improperly formatted JSON configuration file, possibly one that is empty. If you correct the formatting of that file or remove the reference to it, this should not happen. (Look for files named like ".markdownlint.json".)
It sounds like your project or your configuration are referencing an improperly formatted JSON configuration file, possibly one that is empty. If you correct the formatting of that file or remove the reference to it, this should not happen. (Look for files named like ".markdownlint.json".)
My project does not have a .markdownlint.json
file.
Guaranteed reproduction:
test/README.md
# Test File:
Hello, World!!!
4. Go to source control tab
5. Click the new file
Source control diff view can be tricky because it represents files as a different type. Can you please tell me the exact steps to reproduce this myself? What project? What file do I open? Etc.?
Our comments crossed paths! Thank you, I will have a look soon!
@PythonCoderAS, I can get this to happen, but only under the EXACT conditions you describe: github.dev (or vscode.dev) accessing a remote repository opening a Markdown file that's being viewed in diff view. If you hit this in any other contexts, please let me know. Otherwise, I think I can detect the problematic scenario and not lint - which was previously the case for diff view so I think something changed in VS Code or its remote repository support. Thank you!
Okay, I can also reproduce this in VS Code Insiders using the Remote Explorer to open the https://github.dev/github/dev repository. That's nice because it means I can work with unminified code and make changes more easily. I think there's a different/related problem with this scenario that will also be resolved by the change I have in mind.
If I open a brand new Markdown file in the Source Control diff view on
github.dev
: