For the new spec, examples is an array that get's rendered as a dropdown of options, please advice if this is how the UI should appear.

CC: @peterjan @lukechampine

@0ex-d I took a quick look at how we use examples and suggest we drop them where they no longer make sense in OpenAPI 3.1.0. We do need to ensure that when we remove an example, the schema still specifies the type and any patterns or constraints that the field must meet.

For instance, if an object has a field like blockheight, I sometimes specified example: 506412 to make the output less dull, as it would otherwise display blockheight: 0. It doesn't make sense to rewrite such examples into an examples object in 3.1.0. In such cases, you can remove the examples entirely.

@0ex-d did this comment answer your question? If you don't want to update the PR I can add the changes for you so we're on v3.1.0. In any case, many thanks for bringing this to our attention and opening the PR.

Thank you for the feedback. Oh yes i'm unable to make commit at this time, please go ahead and make the update.