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.

Route prefixing does not appear to work for dotnet core

See original GitHub issue

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)]

Issue Analytics

State:
Created 5 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

cromocommented, Aug 28, 2018

True, ActionResult<TValue> was added in 2.1. That may further complicate a compound template. In general, I’d prefer the complexity of a single template (up to a point) over having to maintain multiple templates in parallel. Though maybe there’s a way to split out the differences into different partials that get included in the same skeleton, reducing duplication while still splitting out the details?

0reactions

altsocommented, Aug 29, 2018

@RSuter Please note that action method could also return IActionResult since version 1.0 and it’s also not supported.