[DCR]: Enabled plugins for other protocols
Open
Nobody has claimed this yet.
Area:Plugin
Priority:2
Product:dotnet.exe
Product:NuGet.exe
Product:VS.Client
Type:DCR
- Dominant language
- HTML
- Stars
- 1.6k
- Forks
- 276
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 1
Description
NuGet Product(s) Affected
NuGet SDK
Current Behavior
Currently plugin discovery is only enabled for HTTP sources.
Desired Behavior
Plugin should be able to support other protocols, or source types.
Additional Context
Plugin discovery is only enabled for HTTP sources
This should be relaxed to enable other protocols, and it should be up to the plugin to decide whether it can support the protocol.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read src/NuGet.Core/NuGet.Protocol/Plugins/PluginManager.cs at the linked discovery logic and trace how the current HTTP-only restriction is applied. Done means plugin discovery is no longer limited to HTTP sources, with the plugin deciding whether it supports the source protocol; verify the behavior with the relevant NuGet SDK tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100