Jeremy Fiel

@RomanHotsiy are you saying Ajv doesn't evaluate `allOf` unless `type: object` and `properties` keywords are included? I think this is related to our prior discussion of using Ajv 8+ and...

I'm getting the error to display when I add additional properties without using `properties: {}`. Which version of the CLI are you using? I'm on 1.5.0 ```yaml 1. openapi: '3.1.0'...

So a couple things here.. The `allOf` by itself, without any `properties` or `additionalProperties` keyword used is basically an open schema at the root. So you _shouldn't_ have an error...

@tatomyr does the tool compare examples with the response schema? from your comment, it sounds like this validation is not performed but the error provided is highlighting my example external...

Yes, I can show you on slack if you want to see

i've tried to make a solid example of different locations and usage of `examples` in OAS3.0.x and OAS3.1.x based on discussion with Andrew in our call. **I'm asking for Redocly...

I found a workaround to `externalValue` by using `$ref`. it's not super pretty, but it seems to work ok. Because the `examples` collection expects `example` objects, creating the `example` object...

I thnk it's reasonable to expect the use of $ref over externalValue. You're right about the intention is to express non-json/yaml strings. Because it accepts a uri-reference I think checking...

@tatomyr @lornajane any update on this one? It's still occurring for all examples with shared schemas. I'm on win 10.

you can find serialization examples here, multiple types are supported https://spec.openapis.org/oas/v3.0.3#fixed-fields-9