dependabot[bot] on npm_and_yarn
Bump elliptic from 6.5.3 to 6.5… (compare)
RicoSuter on NSwag-Build-1129
RicoSuter on release
Fix JsonSerializerParameterCode… Merge branch 'master' of https:… Use correct path and 7 more (compare)
This returns null if value is null
return "";instead of null if the parameter is null
app.UseSwaggerUi3(p => p.Path = "/")
@RicoSuter - I'm reading the OpenAPI 3 spec, and -- If I'm understanding it correctly -- it does seem to support "objects" as query parameters https://swagger.io/docs/specification/describing-parameters/#query-parameters:
"Query parameters can be primitive values, arrays and objects"
Related to that is how query parameters can be serialized: https://swagger.io/docs/specification/serialization/
PrepareRequestmethods to add the bearer token? and on the
ProduceResponsefor the login method to get and store the token?
@RicoSuter - I am able to reproduce my "home route" problem starting from the sample "SampleOwinWebApiWithSwaggerUi" found here: https://github.com/NSwag/Samples/tree/master/src . Steps: 1) Run the sample and confirm that the home page shows up. 2) Upgrade all NSwag NuGet packages to 13.9.4. 3) In Startup.cs, change the call "UseSwaggerUi" to
UseSwaggerUi3(typeof(Startup).Assembly, s =>
s.Path = "/foo";
s.SwaggerRoutes.Add(new SwaggerUi3Route("My Fancy API v1", "/qwerty/asdf.json"));
Now when you run the project, instead of the home page, you see that it has been "hijacked" by raw Swagger JSON.