Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move /packages/<action> to a different path
See original GitHub issueBased on https://github.com/NuGet/NuGetGallery/issues/3124#issuecomment-232470851 and as discussed in an e-mail thread:
If a package named “Upload” is uploaded, NuGet.org has no way to distinguish between showing the package upload page, or the package details page.
We may consider moving the actions to, for example, /manage/packages/<action> (e.g. /manage/packages/upload) to distinguish these. Of course /packages/<packageid> would remain active.
This conflict will only happen for the number of action methods we have in the /packages route (approximately 4 to 6).
Note that there are various URLs (e.g. docs) pointing to the upload package route which will have to be updated as well.
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The number of references within the docs arent that much and in our new site we can make the change easily
Will cross my fingers for next time then. Cheers mate!