Feature Request - Optional Message Formatters

Within .NET WebAPI, its possible to add custom formatters for the message types, under WebApiConfig.
e.g.

        public static void Register(HttpConfiguration config)
        {
            // Web API configuration and services

            // Web API routes
            config.MapHttpAttributeRoutes();
            config.Formatters.Add(new MessagePackMediaTypeFormatter());

It'd be cool if we could add a formatter to the SwaggerProvider type constructor!

[sergey-tihon]

We still support only application/json but serializer is already configurable - http://fsprojects.github.io/SwaggerProvider/#/Customization#authentication

[github-actions]

🤖 This is an automated response from Repo Assist.

To clarify what's currently available for OpenApiClientProvider (v3):

JSON customisation is supported via JsonSerializerOptions. Every generated client has constructors accepting a pre-built HttpClient and/or JsonSerializerOptions:

// Custom JSON options (e.g. camelCase, custom converters)
let opts = JsonSerializerOptions(PropertyNamingPolicy = JsonNamingPolicy.CamelCase)
opts.Converters.Add(MyCustomConverter())
let client = MyApi.Client(opts)

Custom HTTP handling (authentication headers, delegating handlers, retry policies, etc.) can be provided via a pre-configured HttpClient:

let httpClient = new HttpClient(MyAuthHandler())
httpClient.DefaultRequestHeaders.Add("Authorization", "Bearer ...")
let client = MyApi.Client(httpClient)

Custom serialisation logic (including non-JSON formats) can be achieved by subclassing the generated client and overriding Serialize / Deserialize:

type MyApiClient() =
    inherit MyApi.Client()
    override _.Serialize(value) = MessagePackSerializer.Serialize(value)  // example
    override _.Deserialize(json, retTy) = MessagePackSerializer.Deserialize(json, retTy)

The provider currently generates only application/json request bodies and reads only JSON responses, so full MessagePack/Protobuf support would require changes to OperationCompiler to honour the API spec's content media types. That would be a welcome enhancement — patches are welcome if anyone wants to take it on!

Generated by 🌈 Repo Assist, see workflow run. Learn more.

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@4ea8c81959909f40373e2a5c2b7fdb54ea19e0a5