Steps
openapi: 3.0.0
info:
version: "1.0.0-oas3"
title: example
paths:
/api/callbacks:
post:
responses:
'200':
description: OK
callbacks:
callback:
'/callback':
post:
requestBody:
$ref: '#/components/schemas/callbackRequest'
responses:
'200':
description: OK
components:
schemas:
callbackRequest:
type: object
properties:
property1:
type: integer
example: 10000
Expected
callback renders in UI panel
Actual
Console error TypeError: C.get(...) is undefined
If the line:
requestBody:
$ref: '#/components/schemas/callbackRequest'
is commented out then the callback is rendered without error

The issue can be resolved by changing the callback operation to:
post:
requestBody:
content: # <-------
application/json: # <-------
schema: # <-------
$ref: '#/components/schemas/callbackRequest'
However, it can reasonably be expected that Editor validation should pick up on this.
@shockey ping!
This seems to have regressed

Aplogies. Was using an invalid definition.
Worth noting, for lack of validation errors. But otherwise this issue is resolved...
Tested with
openapi: 3.0.0
info:
version: "1.0.0-oas3"
title: example
paths:
/api/callbacks:
post:
responses:
'200':
description: OK
callbacks:
callback:
'/callback':
post:
requestBody:
content: # <-------
application/json: # <-------
schema: # <-------
$ref: '#/components/schemas/callbackRequest'
responses:
'200':
description: OK
components:
schemas:
callbackRequest:
type: object
properties:
property1:
type: integer
example: 10000
don't scare me like that, @ponelat 馃槃
Locking due to inactivity.
This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.
If you think you're experiencing something similar to what you've found here: please open a new issue, follow the template, and reference this issue in your report.
Thanks!