chore: Extract JSON computation and caching into a separate crate #575
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extract the JSON documentation caching logic from pavexc into a new crate
pavexc_rustdoc_cache.The rustdoc cache was invalidated on every git commit because the database filename included the git SHA ({VERSION}-{GIT_SHA}.db). This was problematic during local development: each commit wiped the cache, forcing expensive re-computation of JSON docs.
The cache fingerprint is now {VERSION}-{SOURCE_HASH} where:
The hash is computed in pavexc/build.rs by automatically discovering path dependencies from Cargo.toml.