-
Notifications
You must be signed in to change notification settings - Fork 325
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
Cannot print to HTML when another extension crashes #834
Comments
Thanks for the feedback. The Markdown Notes extensions uses a non-standard(?) way to Not sure whether it matters 🤔 cc @1354092549 (in case you have some insights into this issue). |
Does the Markdown Notes extensions work well when previewing? |
Just tried on my PC and it seems it is an issue of Markdown Notes (on its activation). We can still see the error message if we do nothing but open a Markdown file.
I haven't used this extension before but from what I can see, it doesn't work in the VSCode's preview tab. (@orangee-wi) |
Generally speaking, that extension is supposed to be shipped with |
VS Code ignores broken extensions: Maybe we can do similar things here vscode-markdown/src/markdownEngine.ts Lines 91 to 96 in 3037848
|
It's okey to just add a try-catch block. And log may be needed. |
What about: // Skip the third-party Markdown extension, if it is broken or crashes.
try {
md = await contribute.extendMarkdownIt(md);
} catch (err) {
console.error(`Skipped Markdown extension: ${contribute.extensionId}\nBecause:\n${err}`);
} |
Problem
What went wrong?
when I print document to html, console reports a err as follows:
and then, I can't find html in my current markdown file path
Expected behavior?
Print document to HTML successfully!
My environment
How to reproduce
Markdown All in One: Print current document to HTML
Help
->Toggle Developer Tools
err is shown in console
Error message in the console
The text was updated successfully, but these errors were encountered: