-
-
Notifications
You must be signed in to change notification settings - Fork 37
Some feature wrongly considered invalid #14
New issue
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
Comments
So the [dependencies.uuid]
features = ["use_std"]
optional = true
version = ">=0.2.0, <0.7.0"
[dependencies.uuidv07]
optional = true
package = "uuid"
version = ">=0.7.0, <0.9.0" but when fetching dependencies from crates.io all we get is: {
"crate_id": "uuid",
"default_features": true,
"downloads": 0,
"features": [
"use_std"
],
"id": 2871490,
"kind": "normal",
"optional": true,
"req": ">=0.2.0, <0.7.0",
"target": null,
"version_id": 427827
},
{
"crate_id": "uuid",
"default_features": true,
"downloads": 0,
"features": [],
"id": 2871491,
"kind": "normal",
"optional": true,
"req": ">=0.7.0, <0.9.0",
"target": null,
"version_id": 427827
} The dependency alias isn't accessible using the api. I don't see an easy way to retrieve that information for now.
It probably makes sense to let the user choose using a config flag called |
For |
Thanks for looking into this. For the diesel one, I don't know if that's actionable but one could get the optional dependencies out of the
|
I think it's worth looking into this, since that would also allow a way to retrieve metadata for path- and git-dependencies. |
So I added a flag to disable invalid feature diagnostics until this is properly fixed. |
Linking rust-lang/crates.io#1539, just so I remember |
Hello,
Current behavior
Some features are considered invalid, but are in fact valid, and documented on the crate's doc.rs page.
For example :
Expected behavior
Features that are listed in docs.rs don't trigger an "Invalid feature" diagnostic
Additional context/Screenshots
Neovim version
nvim --version
Thanks for the great plugin.
Cheers.
The text was updated successfully, but these errors were encountered: