mdbook/crates/mdbook-summary/Cargo.toml

[package]
name = "mdbook-summary"
version = "0.5.2"
description = "Summary parser for mdBook"
edition.workspace = true
license.workspace = true
repository.workspace = true
rust-version.workspace = true

[dependencies]
anyhow.workspace = true
mdbook-core.workspace = true
memchr.workspace = true
pulldown-cmark.workspace = true
serde.workspace = true
tracing.workspace = true

[lints]
workspace = true
Add mdbook-summary This new crate will hold the Summary types and parsing support. 2025-07-21 13:43:56 -07:00			`[package]`
			`name = "mdbook-summary"`
Update to 0.5.2 2025-12-11 11:40:27 -08:00			`version = "0.5.2"`
Add mdbook-summary This new crate will hold the Summary types and parsing support. 2025-07-21 13:43:56 -07:00			`description = "Summary parser for mdBook"`
			`edition.workspace = true`
			`license.workspace = true`
			`repository.workspace = true`
			`rust-version.workspace = true`

			`[dependencies]`
Finish move of summary to mdbook-summary This updates everything for the move of summary to mdbook-summary. There will be followup commits that will be doing more cleanup here. 2025-07-21 13:55:41 -07:00			`anyhow.workspace = true`
Move Book to mdbook-core This moves the Book definition to mdbook-core, along with related types it needs. 2025-07-21 14:47:11 -07:00			`mdbook-core.workspace = true`
Finish move of summary to mdbook-summary This updates everything for the move of summary to mdbook-summary. There will be followup commits that will be doing more cleanup here. 2025-07-21 13:55:41 -07:00			`memchr.workspace = true`
			`pulldown-cmark.workspace = true`
			`serde.workspace = true`
Switch from log to tracing This switches to using the tracing crate instead of log. Tracing provides a lot of nice features which we can take advantage of moving forward. This also adjusts the output fairly significantly. This includes: - Switched the environment variable from RUST_LOG to MDBOOK_LOG. - Dropped the timestamp. I experimented with various different time displays, but ultimately decided to omit it for now. I don't think I've ever found it to be useful, and it takes up a very significant amount of space. It could potentially be useful for basic profiling, but I think there are other, better mechanisms for that. We could consider leveraging tracing itself for doing some basic profiling (like using something like tracing-chrome). - Dropped the target unless MDBOOK_LOG is set. The target tends to be pretty noisy, and doesn't really convey much information unless you are debugging or otherwise trying to adjust the log output. - Added color. - Slightly reworked the way the error cause trace is displayed. - Slightly changed the way html5ever filtering is done, as well as add handlebars to the list since they both are very noisy. You can override this now by explicitly listing them as targets. I still expect that mdbook will eventually change how it displays things to the console, possibly switching away from tracing and printing things itself. However, that is a larger project for the future. 2025-09-12 06:13:45 -07:00			`tracing.workspace = true`
Add mdbook-summary This new crate will hold the Summary types and parsing support. 2025-07-21 13:43:56 -07:00
			`[lints]`
			`workspace = true`