Generated openAPI shows example in application/json instead of specified text/plain

[jiramares]

Describe the bug
Specifying text/plain media type for response causes openAPI shows response example in wrong media type (stilll uses application/json).

To Reproduce
Following endpoint specifies response media type to text/plain:

val ep2 = Endpoint(RoutePattern.GET / "greeting" / string("name"))
    .outCodec(HttpCodec.content[Greeting](MediaType.text.plain))

and generated openAPI shows response as (the media type is right text/plain):

{
  "msg": "string"
}

Expected behaviour
The response example should be:

string

Dependencies:

    "dev.zio" %% "zio" % "2.1.9",
    "dev.zio" %% "zio-http" % "3.0.1"
    "dev.zio" %% "zio-schema" % "1.4.1"

[jiramares]

The same is also true for error channel:

val ep5 = Endpoint(RoutePattern.GET / "greeting3" / nameParam / "exclamation" / boolParam)
        .copy(error = HttpCodec.content[Greeting](MediaType.text.plain) ++ HttpCodec.status(Status.NotFound))
        .outCodec(HttpCodec.content[Greeting](MediaType.text.plain))

the example error response is

{
  "msg": "string"
}

not plain text

string

[987Nabil]

The examples are currently explicitly created for json. We need to make this dynamic by the media type in the codec

[jdegoes]

/bounty $150

[algora-pbc]

💎 $150 bounty • ZIO

Steps to solve:

1. Start working: Comment /attempt #3260 with your implementation plan
2. Submit work: Create a pull request including /claim #3260 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to zio/zio-http!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @ffprivacy	Jan 24, 2025, 8:17:51 PM	#3283

[ffprivacy]

/attempt #3260

Options

• Cancel my attempt

[algora-pbc]

💡 @ffprivacy submitted a pull request that claims the bounty. You can visit your bounty board to reward.