Expand description
NuGet ecosystem implementation for deps-lsp.
§Private/custom feeds (issue #523)
NuGetEcosystem::parse_manifest resolves the manifest directory’s in-repo NuGet.Config
ancestor chain (crate::config::resolve_with_context) after parsing, stamps each dependency’s
deps_core::parser::DependencySource from it, and registers every implied routing chain
against the shared NuGetRegistry — see crate::config’s module doc for the full
<packageSources>/<packageSourceMapping> resolution model. Parsers in parser.rs stay
config-blind (always construct DependencySource::Registry); only this module threads
config resolution in, mirroring deps-pypi’s/deps-cargo’s split.
§Unknown/unresolvable packages
A 404 or otherwise-unknown package must degrade to no diagnostic, no inlay hint, no
error marker (S4) — this already falls out of deps-lsp’s generic error handling around
Registry::get_latest_matching (a fetch error or Ok(None) both simply omit the
package from cached_versions), so no special-casing is needed here.
Structs§
- NuGet
Ecosystem - NuGet/.NET ecosystem implementation.