-
-
Notifications
You must be signed in to change notification settings - Fork 84
Description
Hi, thank you for this great Markdown editor extension — it’s very useful!
I’d like to request a feature that would significantly improve the workflow:
please add support for VS Code’s Custom Editor API (contributes.customEditors).
Currently, the extension exposes a command (markdown-editor.openEditor) but does not register a custom editor with a viewType. Because of that:
the extension does not appear in “Open With”
it cannot be set as the default editor for .md files via workbench.editorAssociations
users cannot configure .md to automatically open in this WYSIWYG editor
If the extension registered something like:
"contributes": {
"customEditors": [
{
"viewType": "markdownEditor",
"displayName": "Markdown Editor",
"selector": [
{ "filenamePattern": "*.md" }
]
}
]
}
Then users would be able to set it as the default editor for Markdown files, and .md files would open directly in this editor without needing to run a command manually.
This would make the extension behave like a first-class Markdown editor in VS Code and greatly streamline the editing experience.
Thanks for considering this! Let me know if you need any testing or example configurations — I’d be happy to help.