You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building an AST from an iterator of jotdown events would give us parsing; converting to a stream of jotdown events would give us rendering, thereby allowing a full rusty roundtrip. Note that until then, you can always use the typescript impl to emit JSON and then render it, using this library just to operate on the JSON in the middle.
The text was updated successfully, but these errors were encountered:
I think this should ideally be implemented in Jotdown and not here. (It's nicer for a parser to depend on an AST crate than an AST crate to depend on a parser).
Furthermore I think when writing this crate you made a bit of an oversight in making all the block and inline types unconstructable for API users because they all have private fields ... (mostly the meta field ... in same cases like BulletList all fields are private). For an AST library I don't see any reason for any fields to be private.
See hellux/jotdown#17
Building an AST from an iterator of jotdown events would give us parsing; converting to a stream of jotdown events would give us rendering, thereby allowing a full rusty roundtrip. Note that until then, you can always use the typescript impl to emit JSON and then render it, using this library just to operate on the JSON in the middle.
The text was updated successfully, but these errors were encountered: