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
Sure, I think it could be useful, and it is easy to feature-gate.
Just like events, the resulting JSON may have breaking changes between
0.x releases so the format can be considered unstable at least for the
time being.
We have previously discussed serde/JSON support for an AST in #17, but
this shouldn't conflict with that. A `serde` feature should be good for
now to enable serde for events and containers. If we later add an AST,
its serde support can be built by enabling both the `serde` and `ast`
features.
I'd like to access the events from Jotdown in JS (via WASM) as JSON. Would you accept a PR to implement optional serde support?
(basically adding
#[cfg_attr(feature = "serde", derive(Serialize, Deserialize))]
toEvent
andContainer
)(precedent for serde support in a markup parser is given by pulldown-cmark having optional serde support)
The text was updated successfully, but these errors were encountered: