RicoSuter/NSwag

Npm CLI runtime parameter conflict

Open

#1,869 opened on Jan 4, 2019

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C# (1,356 forks)batch import
help wantedtype: bug

Repository metrics

Stars
 (7,358 stars)
PR merge metrics
 (PR metrics pending)

Description

Hello,

I have been trying to use the npm cli to generate the swagger definition of an ASP.NET Core using the project file (.csproj) with the aspnetcore2swagger command, but the thing is that when I use the runtime parameter for the npm cli know which version of the "real" cli to use the AspNetCoreToSwaggerGenerator also uses the same runtime parameter and it fails because of that. When I try to use the "NetCore22" runtime I get an error like:

project.assets.json doesn't have a target for '.NETCoreApp,Version=v2.2/NetCore22'

As a workaround I can always generate the nswag.json with the run command.

Contributor guide

Research direction
Investigate the runtime parameter conflict in the aspnetcore2swagger command. Look at how the runtime parameter is passed to both the npm CLI and the AspNetCoreToSwaggerGenerator. Check the source code for parameter handling and see if there is a way to separate or rename the parameters.
Tech stack
csharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70