Skip to content

use goldmark ecosystem to define options#32

Open
Kunde21 wants to merge 1 commit into
masterfrom
goldmark_options
Open

use goldmark ecosystem to define options#32
Kunde21 wants to merge 1 commit into
masterfrom
goldmark_options

Conversation

@Kunde21

@Kunde21 Kunde21 commented Feb 5, 2021

Copy link
Copy Markdown
Owner

Initial idea on adding extensions and render options to markdownfmt.

Allow extensions to register rendering functions.
@Kunde21 Kunde21 linked an issue Feb 5, 2021 that may be closed by this pull request
@karelbilek

Copy link
Copy Markdown
Collaborator

I would not consider goldmark a good example on how to do extensions

will write later when I get more time :D

@Kunde21

Kunde21 commented Feb 5, 2021

Copy link
Copy Markdown
Owner Author

Not the one I would design if we were starting from scratch, but the goldmark ecosystem already exists using this pattern.

@bwplotka bwplotka left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am ok with any of this. Anything that makes our life simpler (: I don't think we are forced to use goldmark pattern. Even what you suggests looks the same on our API level, so does not matter for me 🤗

Up to you, lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Project Goal/Roadmap? Potential Collaboration or known fork

3 participants