v0.2.1

Fixes #5

Now uses proper TOML parsing in caller_crate_root() to avoid a rare edge case.

v0.2.0

Breaking Change

all embedded paths are now crate-relative instead of workspace-relative. This fixes a number of issues with deploying to crates.io and docs.rs, since workspace relative paths break once you are deploying a sub-crate. We were able to properly detect the caller's crate root using this method: https://github.com/sam0x17/docify/blob/ecb7cc87ec2f2670ce61d7dc3cc331310c42b2a6/macros/src/lib.rs#L72-L102

For this reason, we have bumped into the 0.2.x series.

v0.1.16

Adds support for detecting "workspace = {" style workspace declarations in Cargo.toml (previously only [workspace] was detected

Note: this is OK because the workspace crate is a CLI tool, so shouldn't appear as a dependency for any crates

v0.1.15

• fixes #2
• removes prettyplease dependency because we now manually fix indenting problems without the need for an external crate
• the Docifying ... text now only displays when not in test mode
• added doc notes about suggested conventions when using the markdown feature
• added a cfg gate for the auto-generation of README.md for this crate

v0.1.14

Fixes #1

v0.1.13

A few doc tweaks

v0.1.12

Significantly reduce strictness of all dependency version requirements so it is easier to use this crate in a variety of circumstances

v0.1.11

Use less strict version bound on termcolor

v0.1.10

• fixes terminal color support for the Docifying message, with fallbacks in case there is no terminal color support
• adds compile errors for blank input path or blank output path on compile_markdown (this prevents some weird IO stuff that happens otherwise in some cases)

v0.1.9

• hotfix to prevent docs.rs build failure https://docs.rs/crate/docify/0.1.8/builds/823704
• docs.rs uses a read-only file system, so docify will now only overwrite a file if the new content will actually be different than the original content, allowing for things like dynamically generated README.md files, as long as both the template and the output file are tracked in the git repo