We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document-features
Hi, and thanks for a great crate!
The docs suggests adding this to your Cargo.toml:
Cargo.toml
## Enable this when building the docs document-features = { version = "0.2", optional = true }
The problem with this is that it breaks cargo check:
cargo check
7 | #![doc = document_features::document_features!()] | ^^^^^^^^^^^^^^^^^ use of undeclared crate or module `document_features`
I would suggest updating the docs to instead just have
document-features = "0.2"
unless there is some way to get around the cargo check issue that I'm not aware of
The text was updated successfully, but these errors were encountered:
The docs suggest also to use cfg_attr in that case.
cfg_attr
You could use
#![cfg_attr(feature = "document-features", doc = document_features::document_features!())]
If you think the docs are not clear enough feel free to make a suggestion :-)
Sorry, something went wrong.
Ah, I didn't read the far, just copy-pasted the first thing I saw :P
I made a PR where I suggest we always use the more verbose #![cfg_attr(feature = "document-features", doc = document_features::document_features!())]
a83f3c4
Successfully merging a pull request may close this issue.
Hi, and thanks for a great crate!
The docs suggests adding this to your
Cargo.toml
:The problem with this is that it breaks
cargo check
:I would suggest updating the docs to instead just have
unless there is some way to get around the
cargo check
issue that I'm not aware ofThe text was updated successfully, but these errors were encountered: