All the argument names are missing in the Command arguments section, you can figure it out if you scroll up and down, but it would be nice to have it specified directly.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hi @david-s-svedberg , are you referring to the custom NuGet Command task? If so, that lets you use whichever NuGet command you'd like, with whatever arguments you need. Specifying all of these would be tough I think.
Hi, no. Hard to describe but if you look under the Argument sektion there's a table where the first column is Argument, in that coumn I would expect the name of the argument to be listed, but instead there's a short description. The value of the first row is
Path to solution, packages.config, or project.json
but the argument you need to use is
restoreSolution
Sure you can figure this out by scrolling up and looking at the YAML snippet, but it takes some guesswork and scrolling.
It looks like it's the same for all the Tasks.
Can confirm, the tables first column should be the argument name but it is missing.
@RehanSaeed, @david-s-svedberg, thanks for the feedback. I currently have a backlog item and branch I'm working on to straighten out the inputs and updates. I will let you know when that will be pushed to live :)
@RehanSaeed, @david-s-svedberg, thank you again for the feedback! I've update the documentation and you should see it live within 24 hours.
I'm closing this issue for now and I hope you will open a new issue if you have any more feedback!
Most helpful comment
Hi, no. Hard to describe but if you look under the Argument sektion there's a table where the first column is Argument, in that coumn I would expect the name of the argument to be listed, but instead there's a short description. The value of the first row is
but the argument you need to use is
restoreSolutionSure you can figure this out by scrolling up and looking at the YAML snippet, but it takes some guesswork and scrolling.
It looks like it's the same for all the Tasks.