swagger | Swagger client generator | REST library

In the OpenAPI docs about parameter serialization there's a short section about how to serialize query, path, header and cookie parameters with different styles. The schema of these parameters are described as OpenAPI flavoured json schema, which allows infinite nesting of objects and arrays. I haven't found any mention about how to deal with these in the docs:

https://swagger.io/docs/specification/serialization/

Let's assume the JSON schema provided for any of the parameters is like this:

I am using swagger-ui with express and they use different forms for url paths.

Express uses: "/api/:param1/:param2"

and

Swagger specification uses: "/api/{param1}/{param2}"

In javascript, how would I replace all instances of parameters in an express string with the {} style for the swagger path string.

I tried to inject my own service in my api controller, but it throws an InvalidOperationException. It is unable to resolve the service. (.NET 5)

What I am doing wrong?

When trying to call an ASP.NET method from the client using $.ajax it gives the following error "Failed to load resource: the server responded with a status of 405 ()" knowing that the client and the API are both running on the same domain "localhost:4500", I followed the procedure I found in this Microsoft docs "https://docs.microsoft.com/en-us/aspnet/core/tutorials/web-api-javascript?view=aspnetcore-5.0 " and added the wwwroot folder to avoid the CORS issue but still can't call the API methods through the $.ajax method in javascript.

I tested the backend code through swagger and it was working just fine.

this my backend controller code:

In my GCP project, I have a python API running in a docker container (using connexion). I want to expose the API (with an API key) using API Gateway.

When I deploy the docker container with --ingress internal, I get Access is forbidden. on API calls over the Gateway. So the API gateway cannot access the Google Run container. When I use --ingress all, all works as expected, but then my internal API is accessible from the web, which is not what I want.

I created a service account for this:

I have my API project with ASP.NET Core (.NET5). Everything is working fine and the Swagger page shows all the APIs. Now, in a controller I want to add a function to export an Excel file. The code in the controller is this:

I want to group api endpoints based on tags in Nest js such that all employee endpoints under Employee tag, all site endpoints under Site tag etc. Currently, all my endpoints are under default tag. I am using Swagger in Nest js. Can anyone provide best practice to implement it.

When I request any API endpoint from Swagger UI give me the following error

System.InvalidOperationException: No authenticationScheme was specified, and there was no DefaultChallengeScheme found. The default schemes can be set using either AddAuthentication(string defaultScheme) or AddAuthentication(Action configureOptions).

at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)

at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)

at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)

at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)

at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)

at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

HEADERS

=======

Accept: /

Accept-Encoding: gzip, deflate

Accept-Language: en-US,en;q=0.5

Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJVc2VySWQiOiIzIiwiTG9naW5JZCI6ImFkbWluIiwiVXNlclR5cGVJZCI6IjEiLCJFbWFpbCI6ImEiLCJNb2JpbGUiOiJhIiwianRpIjoiMWU1MDY3ODAtMWRjNS00MDYzLWFkMTktMDdlMjg4MzAxOWVjIiwiZXhwIjoxNjIzNDYzNjQ4LCJpc3MiOiJlZHVjYXJlLmNvbSIsImF1ZCI6ImVkdWNhcmUuY29tIn0.G2-D_oIdwUDw_3iz87jxWBIMabFpLlR5ASjCr109kNM

Connection: keep-alive

Host: localhost:21068

Referer: http://localhost:21068/swagger/index.html

the Swagger configuration is given below

I created the Webapp API, configured Docker-compose to upload the 3 containers with the database, api and web app. I am now facing a problem with converting decimal values.

In my development environment, when typing a value with decimal places everything goes normal (23,14). See the example in the images: When I upload the containers, this behavior is different and when I put the same value in the container application, it treats the value differently. See the example in the image below.

Both the api and the webapp were configured to take the pt-BR localization pattern, however, in the container this configuration seems to be ignored.

WEBAPP