-
-
Notifications
You must be signed in to change notification settings - Fork 682
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
[Feature Request] plugin-md-enhance is too large, perhaps it needs to be split #4130
Comments
I actually prefer function spliting, e,g. I will split imgMark imgSize and figure into one plugin called plugin-markdown-img. Here are my plans:
|
Comparing the more complex aspects of splitting is challenging, especially with elements like Considering these functions are relatively simple and independent, perhaps they can be separately implemented in the upstream e.g:
|
Checklist
Describe the feature
First of all, thank you to markdown enhance for providing powerful functionality support to vuepress markdown! However, it must be said that this plugin has now become very large and cumbersome, making maintenance increasingly difficult. Perhaps it is time to consider splitting it up.
My suggestion is to consider splitting from various perspectives such as new syntax, grammar extensions, third-party dependencies, resource embedding, and content container types.
For example, these combinations can be used as individual plugins.:
hint
,github alerts
, [code-group
];sup
,sub
,task list
,footnote
,mark
,spoiler
,include
;attrs
,imgSize
,imgMark
,obsidianImgSize
,imgLazyload
;breaks
,linkify
,figure
,stylize
;katex
,mathjax
(optional deps);chart
,echarts
,flowchart
,markmap
,mermaid
,plantuml
(optional deps);code-group
],code-demo
;kotlin-playground
,vue-repl
,typescript-playground
Additional context
No response
The text was updated successfully, but these errors were encountered: