Modules applying/not-applying to already marked blocks about markdown HOT 7 CLOSED

You would add Emoji as an inline element this means it will only be parsed with blocks that allow inline elements. Code blocks are not parsed for inline elements obviously so this should work all as expected.

Add the : marker and implement a parsing function for it and you'll have emoji support working ;)

from markdown.

Oh, cool about Emoji.

But modules can be different. Some will need recurse processing in already processed (by other modules/rules) blocks, some won’t.

from markdown.

can you give an example?

from markdown.

For example, we have typography tools like SmartPants, which replace "these" quotes to “these”.

In some cases we need them to process already processed blocks and inline elements: citation blocks, emphased inlines, hyperlink texts and so on.

In some cases we need them not to process: code blocks, code inlines, auto-hyperlinks (only web address provided).

This is for one module. There can be very many variations when new modules appear.

Ideally, when creating module we can have options defining whether to process which blocks, do processing before or after other processings are done and so on.

from markdown.

Looks like you are thinking of this like many other markdown parsers work using regex and processing each element type at a time over the complete text. This library works differently by checking for the next beginning element and parsing it by deciding whether to parse the contents as markdown or not.
This is what inline markers are used for. They mark beginning of an element and the associated parse function will handle everything until the end of the element.

from markdown.

Know about modern Parsedown approach.
OK, I’ll try to implement Emojis for this Markdown (as I need ’em in one of my projects) and then probably I’ll be more armed and experienced :-)

This issue is not matter of approach, regexp or parsedown, whatever. It’s more about architecture of modules: where they apply and when.

from markdown.

Imo this is solved by adding the parsePlainText() method in 0eac7ba#diff-037865b8555f7db5ac9338cfb5be7466R258

from markdown.