This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
alternative registries are not taken into account #41
Assignees
Milestone
Comments
|
Hi @arturoc , |
|
Yeah currently it'd already be great if one could silence git-based errors. |
serayuzgur
added a commit
that referenced
this issue
Nov 19, 2019
- Rate limiting should not trigger error messages [#65](#65) - Fetch Errors and constant error messages when viewing Cargo.toml with conflicts [#61](#61) - Alert always happen when I add deps to Cargo.toml [#59](#59) - `No versions found` error should be less intrusive [#58](#58) - alternative registries are not taken into account [#41](#41)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Crates from alternative registries are parsed as comming from crates.io so the versions shown are from crates.io instead of the altenarive registry but also if the package doesn't exist in crates.io an error is shown every time the file is modified
To Reproduce
Add a crate from an alternative registry which has a different max version there than in crates.io or doesn't exist in crates.io, only in the alternative registry
Expected behavior
Ideally that versions are parsed from the alternative registry but at least that the alternative registry is detected so those crates don't show any max version and no error is shown if they don't exist in crates.io as happens with packages from git sources
Platform:
Additional context
alternative registries are still not stable but will be in the next release, 1.34
The text was updated successfully, but these errors were encountered: