Implement push to v3 (adoption issue)
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Currently you have to properly configure your push url to the v2 endpoint. For some nuget servers (like TFS/VSTS) this URL it not really easy to guess (In fact it took quite a while for myself to figure it out).
To improve experience for newcomers I suggest the following:
When a v3 URL is given we do not try to "guess" anything but find the correct url via index.json, by using the url with the type @type=PackagePublish/2.0.0. We basically have most of the code for this already in place. It is basically a matter of refactoring and using the existing functionality when pushing.
Expected behavior
paket push just works with a v3 url
Actual behavior
You have to use fiddler and nuget.exe to figure it out
Known workarounds
Know the correct url for your server
Contributor guide
No contributing guide indexed for this repository
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
Start with the existing Paket push implementation and the functionality that reads a NuGet v3 index.json. Trace how the PackagePublish/2.0.0 URL is discovered and used during pushing. Done means paket push accepts a v3 URL and selects the publish endpoint without requiring users to know the server's v2 URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100