You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
For an AspNetCore.Mvc api, the request and response json serializer settings are configured using an options specific to the AspNetCore.Mvc packages.
In the Microsoft.AspNetCore.OpenApi packages, the open api document services rely solely on the Microsoft.AspNetCore.Http.Json.JsonOptions value to control json serializer settings. As mentioned in the related issue, this was done to avoid the need to reference the .Mvc packages from the OpenApi packages.
However, requiring consumers to always change their Microsoft.AspNetCore.Http.Json.JsonOptions to match their Mvc ones in order for the open api spec doc generation to work is not viable in many situations. Changing the Microsoft.AspNetCore.Http.Json.JsonOptions has additional ramifications as it would also change behavior of outbound http calls from an aspnet core mvc api to other services.
Describe the solution you'd like
The Microsoft.AspNetCore.OpenApi packages should support json options configuration independently of the overall Microsoft.AspNetCore.Http.Json.JsonOptions configuration.
Continuing to default the values to match those of the service container's Http.Json.JsonOptions would be acceptable, but the AddOpenApi() service collection extension methods should support specifying the options to use without requiring a global default change to the behavior of the application
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Related issue: #57891
Problem:
For an AspNetCore.Mvc api, the request and response json serializer settings are configured using an options specific to the AspNetCore.Mvc packages.
In the Microsoft.AspNetCore.OpenApi packages, the open api document services rely solely on the Microsoft.AspNetCore.Http.Json.JsonOptions value to control json serializer settings. As mentioned in the related issue, this was done to avoid the need to reference the .Mvc packages from the OpenApi packages.
However, requiring consumers to always change their Microsoft.AspNetCore.Http.Json.JsonOptions to match their Mvc ones in order for the open api spec doc generation to work is not viable in many situations. Changing the Microsoft.AspNetCore.Http.Json.JsonOptions has additional ramifications as it would also change behavior of outbound http calls from an aspnet core mvc api to other services.
Describe the solution you'd like
Additional context
No response
The text was updated successfully, but these errors were encountered: