RicoSuter/NSwag

Route prefixing does not appear to work for dotnet core

Open

#1,386 opened on Jun 15, 2018

View on GitHub
 (10 comments) (0 reactions) (0 assignees)C# (1,189 forks)batch import
help wantedproject: NSwag.CodeGeneration.CSharp (Controllers)type: enhancement

Repository metrics

Stars
 (6,291 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

We are attempting to use SwaggerToCSharpControllerGenerator to generate a dotnet core compatible web api. Unfortunately we have a slight problem with route prefixing. The generator is generating the code [routeprefix('v1')] whereas, I believe that using dotnet core this needs to be [route('v1)]

Contributor guide

Research direction
Investigate the SwaggerToCSharpControllerGenerator code to locate where routeprefix is generated and change it to output [Route("v1")] for ASP.NET Core targets.
Tech stack
csharp
Domain
apibackend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#ASP.NET Core routing basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70