Closed chrysn closed 10 months ago
Argh, yeah I see...
It does do some mangling. Idk how to solve that except for duplicating the readme...
They do work on GitHub, but in the crate the root changes to the crate folder.
Thanks! I fixed it in the last release with hard links instead of relative links
The links on https://crates.io/crates/device-driver/0.5.0 for the various examples go 404 -- they contain twice the
/device-driver/
path component.I'd file this as a PR, but I have no clue as to which magic makes the relative references in there work on crates.io in the first place – is there some regeneration of the README at release time involved? (Might be related to the tags not being set).
If there is no file mangling magic, please let me know and close this issue; then, this must be some crates.io mixup, maybe as part of processing the readme.workspace attribute.