markdown-rs
yaml-rust
| markdown-rs | yaml-rust | |
|---|---|---|
| 5 | 4 | |
| 791 | 597 | |
| - | - | |
| 7.1 | 0.0 | |
| 28 days ago | about 2 months ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
markdown-rs
-
Ubiquity (v0.3.0) - I made a cross-platform markdown editor to learn some Rust. It uses Yew, Tauri, Tailwind and DaisyUI. Currently available on Windows, Linux and the web.
I used the markdown-rs crate for Ubiquity.
-
Project idea: port markdownlint to Rust
https://github.com/wooorm/markdown-rs for parsing markdown
-
Looking for an extensible markup language (aka Markdown, Asciidoc, ...) implemented in Rust.
Have you considered markdown-rs?
- New CommonMark compliant Markdown parser in Rust with ASTs and extensions
yaml-rust
-
Project idea: port markdownlint to Rust
Either https://github.com/chyh1990/yaml-rust or https://github.com/dtolnay/serde-yaml for parsing the YAML config file that markdownlint uses
-
Borrow checker not liking recursive walk through a HashMap
Here's the Rust code so far -- the commented portions are my intent via pseudocode. This is part of an implementation where there's a _yaml_hash member that points to yaml_rust's underlying LinkedHashMap. (Also using anyhow's bail! and Result.)
-
How to deal with unmaintained crates? (eg. yaml-rust)
The first thing I did was to find the crate yaml-rust and it seems it isn't really maintained anymore. It has not been updated in a year and there's a lot of PR's and unresolved issues, the CI is broken... So here is my open ended question.
-
YAML and Configuration Files
Currently, my main concern with YAML is that, by the spec, comments are not attached to a particular node (see https://yaml.org/spec/1.2/spec.html#id2767100). As a result, a lot of YAML parsers (like https://github.com/yaml/libyaml and https://github.com/chyh1990/yaml-rust) only filter out the comments during the parsing phase. This makes it less than ideal for a use-case where the configuration file is expected to be modified by both programs and humans.
TOML makes it more trivial to associate comments with a node. This is mainly because the language is simpler though, as the spec is not explicit about that (https://github.com/chyh1990/yaml-rust).
What are some alternatives?
tauri-sys - Bindings to the Tauri API for projects using wasm-bindgen
serde-yaml - Strongly typed YAML library for Rust
comrak - CommonMark + GFM compatible Markdown parser and renderer
serde - Serialization framework for Rust
clap-rs - A full featured, fast Command Line Argument Parser for Rust
strictyaml - Type-safe YAML parser and validator.
md.rs - A Markdown parser library in Rust
cue - CUE has moved to https://github.com/cue-lang/cue
markdownlint - A Node.js style checker and lint tool for Markdown/CommonMark files.
libyaml-rust - LibYAML bindings for Rust
taffy - A high performance rust-powered UI layout library
ytt - YAML templating tool that works on YAML structure instead of text