question-mark
Stuck on an issue?

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.

Unify names of argument --source-feed vs -s,--source

See original GitHub issue

Steps to reproduce

Try:

dotnet nuget push -h

Usage: dotnet nuget push [arguments] [options]

Arguments:
  [root]  Specify the path to the package and your API key to push the package to the server.

Options:
  ...
  -s|--source <source>           Specifies the server URL
  ...

then:

dotnet tool install -h

Usage: dotnet tool install [options] <PACKAGE_ID>

Arguments:
  <PACKAGE_ID>   NuGet Package Id of the tool to install.

Options:
  ...
  --source-feed <SOURCE_FEED>   Adds an additional NuGet package source to use during installation.
  ...

Expected behavior

dotnet tool install should have -s, --source switch instead of --source-feed without (unreserved) -s alias

Actual behavior

dotnet nuget push has -s, --source, and dotnet tool install has --source-feed.

Environment data

dotnet --info output:

.NET Core SDK (reflecting any global.json):
 Version:   2.1.300-preview3-008443
 Commit:    1e2e8138b9

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:39 (21 by maintainers)

github_iconTop GitHub Comments

2reactions
tmdscommented, Apr 25, 2018

It would be nice if dotnet tool install provided a --source parameter that is consistent with the other commands: i.e. not additive.

I like this consistency since we are not going to remove --source parameter from the other commands and we are used to how it behaves.

I see this when changing some scripts. I want to pass the same feeds to dotnet tool install as I am passing to dotnet restore and suddenly I need to deal with different semantics 😕

Whether it makes sense to have an additive source parameter is a different question. A --source-feed (I personally like --add-source) can be added to dotnet tool install and other commands if it useful.

1reaction
livarcocccommented, Apr 27, 2018

Sounds good to me.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Git : get destination and source branche name during ...
Is there a way to get the destination branch name and the source branch name during a merge from a client-side hook to...
Read more >
Source Functions | Segment Documentation
Source functions allow you to gather data from any third-party applications without worrying about setting up or maintaining any ...
Read more >
Unified Data Model field list | Chronicle Security
This document provides a list of fields available in the Unified Data Model schema. When specifying a field, use the following format: <prefix>....
Read more >
Merge (Data Management)—ArcGIS Pro | Documentation
Use this tool to combine datasets from multiple sources into a new, single output dataset. All input feature classes must be of the...
Read more >
Git branch policies and settings - Azure Repos
Branch policies and settings provide teams with the means to protect their important branches.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found