Bnchi

Thanks for you work @wooorm it will be so handy to have this as crate/feature, is there any plans soon to add it into the project ?

Yeah, my bad I asked that question because the comment was in 2023 and I thought there might be other plans. I have time now which I can spend to...

@wooorm I know a little bit about parsers and I read part of the JS implementation, appreciate if you can help me here and let me know if my intuition...

Hmm the _Visitor_ abstraction might be a nice to have and is not needed for this specific case since we're only going to be serializing straight to markdown so we...

If I understood what you said correctly does that mean _state_ is conceptually a state machine that track where you're in the tree and it's used to call the correct...

Thanks for the clarification @wooorm I made a small initial commit to lay down the foundation to what I think make sense to serialize in rust : https://github.com/bnchi/markdown-rs/commit/973f760051d2e31a3beb3d10226cd3fcbe215a21 I'm thinking...

I'm working on #127 and was thinking of making the options passed to the _to_markdown_ function also configurable using a builder I was thinking that once the user call _build_...

What I have in my head is along the lines of this code : ```rust struct Options { strong: char, } ``` ```rust struct OptionsBuilder { strong: char, } impl...

In the JS implementation _check_strong_ is being called during serialization here : https://github.com/syntax-tree/mdast-util-to-markdown/blob/main/lib/handle/strong.js#L24 using the above method I believe we can check if the user provided the valid options at...

> If you only check in build, then it is still possible to pass invalid options? The _Options_ fields will not be pub that's the user from a different module...