You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature deprecation strategy #1114 comment from @UziTech recommends "best way" (sorry, knee-jerk reaction whenever someone says "best way" 😆) related to a possible to-be architecture.
Capture at least a basic (no members or functions necessary) class diagram (like??) model illustrating Marked's current architecture.
Think @intcreator should get first refusal since he seems most passionate about needing an architecture (and architect) to be able to get up to speed in understanding the code easier. I know you said you've only had a couple year's experience with JS but that'll be fine, that's why we have review.
Let us know?? (No harm, no foul.)
The text was updated successfully, but these errors were encountered:
Use typescript make the Classes and helper functions export more clear and useful.
And make plugins more easy. It is very hard to write plugin for marked currently.
I have to use the kramed to do a simple task with a little patch, see the hacked code front-matter-markdown, The kramed still need to reconstruct too.
Tokenizer, Parser, Render Classes and userful helper functions.
Marked version: 0.3.17
Markdown flavor: n/a
Proposal type: other
What pain point are you perceiving?
#1089, #1096, #1097
What solution are you suggesting?
Capture at least a basic (no members or functions necessary) class diagram (like??) model illustrating Marked's current architecture.
Think @intcreator should get first refusal since he seems most passionate about needing an architecture (and architect) to be able to get up to speed in understanding the code easier. I know you said you've only had a couple year's experience with JS but that'll be fine, that's why we have review.
Let us know?? (No harm, no foul.)
The text was updated successfully, but these errors were encountered: