Custom parser options

[ReyMagos]

Thank you for the great extension! It really helps!

So, I need to parse some custom markdown tokens from own tokenizer extension. I can add functions to custom renderer but is there an option to make parser recognize new token types?

[tanmayaBiswalOdiware]

What are you trying to parse here besides the usual?

[ReyMagos]

I have keyword that indicates following block should be wrapped into my component. And I need to handle this keyword in parser to properly set token type.

[sibiraj-s]

Hi, Currently the parser accepts only tokens that are parsed by marked. See

marked-react/src/Markdown.ts

Lines 39 to 41 in 6fbd187

	const tokens = props.isInline
	? Lexer.lexInline(markdownString, lexerOptions)
	: Lexer.lex(markdownString, lexerOptions);

I'am open to suggestions to solve this, if marked allows to extend and parse into custom tokens, we could allow here as well. Why not.

[tanmayaBiswalOdiware]

I wondered for a while what you might be able to do here. Reading the marked documentation, you can see - we need to define a custom object as shown in the example. Maybe you can expose the lexar variable to the client in order to return a custom token. I am not completely sure how we go about doing that. Perhaps you can test it :)

[sibiraj-s]

Currently I am working something with <Marked instance={customMarkedInstance} /> and planning to support extensions as well but it can be only done after markedjs/marked#2805, because the current @types/marked is messed up and doesn't exactly reflect marked library giving several errors with typescript.

Boy its not easy. I'll try but even if I support extensions, It might help your case, but it might not be possible to provide 100% support for extensions, as the renderer part in marked returns html and not react elements so it might be omitted

[punkpeye]

Any updates here?

I think I am running into some related issue.

bent10/marked-extensions#107

It is as if this.lexer is not shared between inline and blocker parser?

[sibiraj-s]

Some marked extensions cannot be used, since the renderer is different. Marked extensions returns html and here react component is expected.

You can now to <Markdown instance={your marked instance} to override the default instance which allows some customization.