📣 Plans for V2

[JohannesKaufmann]

The V2 of the library is in the works. It is a rewrite from the ground up — even more accurate than the current version.

Some new features:

• Nested lists: More edge cases around (deeply) nested lists are supported
• Smart escaping: Only escape characters if they would be mistaken for markdown syntax
• ...

➡️ What are some things that you would want to see? How could the API be improved? What currently annoys you?

[benmyles]

I'm building a text-only browser using this and playwright, and I'd love some kind of support for forms (showing inputs and names / ids so that the correct element can be later "clicked").

[JohannesKaufmann]

@benmyles sounds cool!

That is probably not something I would add to the core for now. But it can be implemented with some rules & then packaged as a plugin.

Let me know if you have some questions while doing this...

[ilovesusu]

What is the current stage of implementation? Is it possible to upload code to the dev branch?

[JohannesKaufmann]

Hi @ilovesusu,

the V2 already works quite well. But it is still a prototype and there is still a lot of manual testing needed.

The reason I haven't made it public yet: The public API is still undecided. I don't know if I want to keep the Options or use a more functional options pattern.

And once I release an early version, other people would use it — and depend on it. Then every change is going to break existing programs 🤷‍♂️

[ilovesusu]

I think it's possible to make the project public and use dev branches to allow people to collaborate on contributions
Stabilized before releasing the full version