Yes - this is exactly correct. For multiple examples to be rendered you need to provide all of them. It's a bit of a limitation.

I'm currently trying to get rid of this

"oneOf": [ singleRef ]

- not only because of esthetic reasons, but mainly because oapi2 converters don't handle it (and it seems that http4k oapi3 generator is better than oapi2/swagger). Any ideas how to do that?

ah - the latest version actually removes the oneOf for OA2 because it isnt' supported

cool. Any plans to port it for oapi3? Imho removing oneof for a single element would look cleaner

no - there's no harm in keeping it for OA3 so will leave it.

yeah, I agree that it's conform to the spec. The benefits from still removing it would be increased portability and it would also look simpler and closer to what a manually crafted oapi file would look like