v0.2.8

Upgrades to derive-syn-parse 0.2.0 (syn 2.0 support)

v0.2.7

updates toml to 0.8

v0.2.6

Fixes #18, enabling the use of nested #[docify::export]'s within each other

v0.2.5

• Adds #[docify::export] (#15)
• Fixes indentation bug (#16)

v0.2.4

• fixes #9
• adds support for exporting items that appear in traits and within impl blocks. These follow the same rules about collisions in the global namespace of the file, so if the same trait is impled multiple times in the same file, items from the first impl will take priority unless a unique disambiguation name is provided

v0.2.3

Full fix for #7 / multi-byte UTF-8 characters now fully supported by docify

v0.2.2

Partial fix for #7

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