-
-
Notifications
You must be signed in to change notification settings - Fork 190
Does not work in vscode.dev/azurerepos #367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The message for 1 and the exception for 3 are coming from VS Code, not this extension. The part you show in 2 that works is this extension. :) I think we need to figure out why VS Code doesn't like your repository. Can you please provide a link I can use to reproduce this? Have you tried it on github.dev? That's a similar site that I know works. Also, I'd suggest trying this without any extensions loaded. I think you will still get the error from one which will confirm that that's coming from VS Code itself. |
I've double-checked and confirm the scenario you describe works in If you can provide a reproduction on |
Hello @DavidAnson ! Thanks for the fast reply, and sorry for my slow one ;) |
I can't reproduce the problem with your link. The project appears empty to me, but I can add a new Markdown file and it lints successfully and without exceptions. The stack you show above has two frames and both are from VS Code, not markdownlint. Please copy+paste the content of the other Output categories when this happens - maybe there are clues there. I'd also recommend trying to reproduce this on |
Hello!
I access git repos stored in Azure repos using the browser-only version of vscode, e.g.
https://vscode.dev/azurerepos/myOrg...
.I run in a few, i think related issues:
i use
i tried adding
.markdownlint-cli2.jsonc
and.markdownlint.json
but it had no influence on it.Since the plugin has this warning
i realize that functionality may be limited, but then again it starts up properly, and only then stops to work.
Thank you in advance :)
The text was updated successfully, but these errors were encountered: