1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303
//! The `readme-sync` crate makes it easy to add an integration test //! that checks that your readme and crate documentation are synchronized. //! //! # About //! //! This crate provides several abstractions for readme and documentation content //! as well as multiple readme and documentation parsing and transformation functions. //! With them, readme and documentation are transformed into a set of markdown nodes //! that are expected to be the same. //! Their equality can be checked with the `assert_sync` function, //! which also provides useful diagnostic messages about the differences found. //! //! It accepts not only inner doc-comments (`//!`) but also //! inner doc-attributes (`#[!cfg(...)]` and `#[!cfg_attr(...)]`). //! This is useful when some doc-tests require certain features to compile and run. //! //! # Usage //! //! First, add the following to your `Cargo.toml`: //! //! ```toml //! [dev-dependencies] //! readme-sync = "0.0.1" //! ``` //! //! Note that `cargo build` and `cargo test` use features from dev-dependencies, //! so if you want to test your crate without them (for example in `no_std` environment) //! you can use `readme-sync` with `default-features = false`. //! See [this](#how-to-prevent-readme-sync-dependency-features-enabled-for-dependencies-of-my-crate) //! FAQ section for more details. //! //! Then add an integration test using the necessary readme and docs modifiers, //! and check their synchronization using the `assert_sync` function. //! #![cfg_attr( all( feature = "codemap", feature = "codemap-diagnostic", feature = "glob", feature = "proc-macro2", feature = "pulldown-cmark", feature = "serde", feature = "syn", feature = "thiserror", feature = "toml" ), doc = "```rust" )] #![cfg_attr( not(all( feature = "codemap", feature = "codemap-diagnostic", feature = "glob", feature = "proc-macro2", feature = "pulldown-cmark", feature = "serde", feature = "syn", feature = "thiserror", feature = "toml" )), doc = "```rust,compile_fail" )] //!# /* //!#[cfg(test)] //!#[test] //!fn readme_sync_test() { //!# */ //! use readme_sync::{assert_sync, CMarkDocs, CMarkReadme, Config, Package}; //! //! let package = Package::from_path(env!("CARGO_MANIFEST_DIR").into()).unwrap(); //! let config = Config::from_package_docs_rs_features(&package); //! let readme = CMarkReadme::from_package(&package).unwrap(); //! let docs = CMarkDocs::from_package_and_config(&package, &config).unwrap(); //! //! let readme = readme //! .concat_texts() //! .remove_badges_paragraph() //! .remove_documentation_section() //! .disallow_absolute_repository_blob_links() //! .unwrap() //! .use_absolute_repository_blob_urls() //! .unwrap(); //! //! let docs = docs //! .concat_texts() //! .increment_heading_levels() //! .add_package_title() //! .remove_codeblock_rust_test_tags() //! .use_default_codeblock_rust_tag() //! .remove_hidden_rust_code() //! .disallow_absolute_package_docs_links() //! .unwrap() //! .use_absolute_package_docs_urls() //! .unwrap(); //! //! assert_sync(&readme, &docs); //!# /* //!} //!# */ //!``` //! //! # Feature Flags //! //! By default, all crate features are enabled. //! //! All crate dependencies are optional and are therefore enabled by features: //! `codemap`, `codemap-diagnostic`, `glob`, `proc-macro2`, `proc-macro2-span-locations` //! `pulldown-cmark`, `serde`, `syn`, `thiserror`, `toml`. //! //! Also, it has `proc-macro2-span-locations` feature that enable `proc-macro2/span-locations` //! feature and allow the crate to show the locations of errors for doc-attributes. //! //! # Other crates //! //! - [`cargo-sync-readme`]: generates readme section from documentation. //! It does not support doc-attributes and does not provide diagnostics. //! But if you just need to synchronize readme and docs text //! or check if they are synchronized it might be a better choice. //! - [`version-sync`]: crate makes it easy to add an integration test that checks //! that README.md and documentation are updated when the crate version changes. //! //! # FAQ //! //! ## Why is the example integration test so long and there is no function that does all this by itself? //! //! Currently, this crate is at an early stage of development //! and common readme and documentation transformations are not yet stabilized. //! //! At the moment, however, it supports wide customization. //! You can specify the paths to readme and docs, their contents, //! the features and transformations used, or use your own transformations. //! //! Any kind of feedback is welcome! //! //! ## Why use `syn` instead of just parsing documentation comments? //! //! Because of `cfg` and `cfg_attr` that are useful for documentation tests //! that require some specific features and can only be compiled with them. //! //! ## Why Markdown instead of text comparison? //! //! It simplifies the Markdown transformations. //! Transformations are necessary, //! because of some differences between readme content and documentation //! including: the presence of a crate name, different heading levels, //! the presence of badges, different relative url root, etc. //! //! ## Why are all dependencies optional? //! //! By default, Rust compiler enable features from dev-dependencies for normal dependencies //! for commands like `cargo test` and `cargo build`. //! As a result, the features used by dev-dependencies are implicitly enabled during testing. //! Because in `readme-sync` all dependencies are optional, //! you can easily protect your crate from implicitly enabled common features. //! //! See [rust-lang/cargo#7916](https://github.com/rust-lang/cargo/issues/7916) for more details. //! //! ## How to prevent `readme-sync` dependency features enabled for dependencies of my crate. //! //! If you use nightly Rust you can simply use `-Z features=dev_dep` flags. //! //! Or, in any Rust release, you can disable all `readme-sync` dependencies with: //! ```toml //! [dev-dependencies.readme-sync] //! version = "0.0.1" //! default-features = false //! ``` //! //! This will help you avoid feature injection from dev-dependencies. //! //! In order to use `readme-sync` functionality in this case, //! you need to add a feature that reenables `readme-sync` default features //! and can be used to run readme synchronization integration tests: //! ```toml //! [features] //! test-readme-sync = ["readme-sync/default"] //! ``` //! //! Then you need to add `test-readme-sync` conditional check to your readme sync integration test: //! ```rust //! #[cfg(all(test, feature = "test-readme-sync"))] //! // ^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ //! #[test] //! fn readme_sync_test() { //! // ... //! } //! ``` //! //! And run it with //! ```bash //! cargo test --features "test-readme-sync" //! ``` //! //! # License //! //! Licensed under either of //! //! - Apache License, Version 2.0 //! ([LICENSE-APACHE](https://github.com/zheland/readme-sync/blob/master/LICENSE-APACHE) or //! [https://www.apache.org/licenses/LICENSE-2.0](https://www.apache.org/licenses/LICENSE-2.0)) //! - MIT license //! ([LICENSE-MIT](https://github.com/zheland/readme-sync/blob/master/LICENSE-MIT) or //! [https://opensource.org/licenses/MIT](https://opensource.org/licenses/MIT)) //! //! at your option. //! //! ## Contribution //! //! Unless you explicitly state otherwise, any contribution intentionally submitted //! for inclusion in the work by you, as defined in the Apache-2.0 license, //! shall be dual licensed as above, without any //! additional terms or conditions. //! //! [API Documentation]: https://docs.rs/readme-sync //! [`cargo-sync-readme`]: https://crates.io/crates/cargo-sync-readme //! [`version-sync`]: https://crates.io/crates/version-sync #![warn( clippy::all, rust_2018_idioms, missing_copy_implementations, missing_debug_implementations, single_use_lifetimes, missing_docs, trivial_casts, unused_import_braces, unused_qualifications, unused_results )] #![no_std] extern crate std; mod badges; mod cmark_data; mod cmark_docs; mod cmark_item; mod cmark_readme; mod cmark_util; mod codemap_files; mod codemap_spans; mod config; mod docs_parser; mod file; mod file_docs; mod manifest; mod package; mod sync; mod tags; mod text_source; #[cfg(feature = "glob")] pub use badges::badge_url_patterns; #[cfg(all(feature = "pulldown-cmark", feature = "thiserror"))] pub use cmark_data::DisallowUrlsWithPrefixError; #[cfg(feature = "pulldown-cmark")] pub use cmark_data::{CMarkData, CMarkDataIter}; #[cfg(feature = "pulldown-cmark")] pub use cmark_docs::CMarkDocs; #[cfg(feature = "pulldown-cmark")] pub use cmark_item::{ CMarkItem, CMarkItemAsModified, CMarkItemAsRemoved, CMarkItemWithNote, CMarkSpan, }; #[cfg(feature = "pulldown-cmark")] pub use cmark_readme::CMarkReadme; #[cfg(all(feature = "pulldown-cmark", feature = "thiserror"))] pub use cmark_readme::CMarkReadmeFromPackageError; #[cfg(feature = "codemap")] pub use codemap_files::CodemapFiles; #[cfg(all(feature = "codemap", feature = "codemap-diagnostic",))] pub use codemap_spans::CodemapSpans; pub use config::Config; #[cfg(all(feature = "syn", feature = "thiserror",))] pub use docs_parser::{ build_attr_docs, build_meta_docs, eval_cfg_predicate, BuildAttrDocsError, BuildMetaDocsError, EvalCfgPredicateError, }; pub use docs_parser::{DocsItem, DocsSpan}; pub use file::File; #[cfg(feature = "thiserror")] pub use file::FileFromPathError; #[cfg(all(feature = "syn", feature = "thiserror"))] pub use file_docs::FileDocsFromFileError; pub use file_docs::{FileDocs, TextRemap}; #[cfg(all(feature = "toml", feature = "thiserror"))] pub use manifest::{BinPathError, TomlParseError, TomlReadError}; pub use manifest::{ Manifest, ManifestBinTarget, ManifestDocsRsMetadata, ManifestLibTarget, ManifestPackage, ManifestReadmePath, }; pub use package::Package; #[cfg(all( feature = "codemap", feature = "codemap-diagnostic", feature = "pulldown-cmark", feature = "thiserror", ))] pub use sync::{assert_sync, check_sync, CheckSyncError, MatchFailed}; pub use tags::codeblock_rust_test_tags; pub use text_source::TextSource; #[cfg(feature = "pulldown-cmark")] use cmark_util::IntoStatic;