pulldown-cmark-to-cmark
| Crates.io | pulldown-cmark-to-cmark |
| lib.rs | pulldown-cmark-to-cmark |
| version | |
| source | src |
| created_at | 2018-02-11 09:30:00.774432 |
| updated_at | 2024-12-11 06:55:08.339195 |
| description | Convert pulldown-cmark Events back to the string they were parsed from |
| homepage | https://github.com/Byron/pulldown-cmark-to-cmark |
| repository | https://github.com/Byron/pulldown-cmark-to-cmark |
| max_upload_size | |
| id | 50647 |
| Cargo.toml error: | TOML parse error at line 30, column 1 | 30 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Sebastian Thiel (Byron)
documentation
https://docs.rs/crate/pulldown-cmark-to-cmark
README
A utility library which translates Event back to markdown.
It's the prerequisite for writing markdown filters which can work as
mdbook-preprocessors.
This library takes great pride in supporting everything that pulldown-cmark supports,
including tables and footnotes and codeblocks in codeblocks,
while assuring quality with a powerful test suite.
How to use
Please have a look at the stupicat-example for a complete tour
of the API, or have a look at the api-docs.
It's easiest to get this library into your Cargo.toml using cargo-add:
cargo add pulldown-cmark-to-cmark
Supported Rust Versions
pulldown-cmark-to-cmark follows the MSRV (minimum supported rust version) policy of pulldown-cmark. The current MSRV is 1.71.1.
Friends of this project
- termbook
- A runner for
mdbooksto keep your documentation tested.
- A runner for
- Share Secrets Safely
- share secrets within teams to avoid plain-text secrets from day one
Maintenance Guide
Making a new release
- Assure all documentation is up-to-date and tests are green
- update the
versioninCargo.tomlandgit commit - run
cargo release --no-dev-version