\r\n\r\n\r\n\r\n### Why is this needed?\r\n\r\nThis is useful for endpoints that accept different request bodies\r\n\r\n### How could it be implemented?\r\n\r\nImplement and show a select element when examples are present in openapi.json:\r\n\r\n```\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/ExamplePost\"\r\n },\r\n \"examples\": {\r\n \"Example 1\": {\r\n \"summary\": \"Creating example 1\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\"\r\n }\r\n },\r\n \"example 2\": {\r\n \"summary\": \"Creating example 2\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\",\r\n \"phone_number\": \"123456789\"\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"required\": true\r\n },\r\n```\r\n\r\n### Other information\r\n\r\nI couldn't find this anywhere in the documentation, but if it is already possible i would like to know how. Thank you!",[2930],{"name":2881,"color":2882},141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.82127684,{"description":2937,"labels":2938,"number":2940,"owner":2867,"repository":2884,"state":2869,"title":2941,"updated_at":2942,"url":2943,"score":2944},"Take the following minimal crashable example:\r\n\r\n```json\r\n{\r\n \"openapi\": \"3.0.0\",\r\n \"info\": {\r\n \"title\": \"Minimal API with Circular Reference\",\r\n \"version\": \"1.0.0\"\r\n },\r\n \"paths\": {\r\n \"/parent\": {\r\n \"get\": {\r\n \"summary\": \"Get a parent\",\r\n \"operationId\": \"getParent\",\r\n \"responses\": {\r\n \"200\": {\r\n \"description\": \"A parent with a child\",\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/Parent\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"components\": {\r\n \"schemas\": {\r\n \"Parent\": {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"string\"\r\n },\r\n \"child\": {\r\n \"$ref\": \"#/components/schemas/Child\"\r\n }\r\n }\r\n },\r\n \"Child\": {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"string\"\r\n },\r\n \"parent\": {\r\n \"$ref\": \"#/components/schemas/Parent\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\nThis is valid openapi spec as can be seen checked using a [validator](https://apitools.dev/swagger-parser/online/). Of course, dealing with a circular swagger requires a form of normalization. \r\n\r\nI am currently using the standard swagger UI, which does nicely deal with circular references. However, as I have moved all my documentation over to vitepress, I would also prefer to maybe include some swagger here and there as it could help make explanations a bit clearer.",[2939],{"name":2878,"color":2879},57,"[BUG] Generator crashes if openapi-spec contains a circular reference","2024-09-28T15:43:59Z","https://github.com/enzonotario/vitepress-openapi/issues/57",0.83325243,{"description":2946,"labels":2947,"number":2951,"owner":2867,"repository":2902,"state":2869,"title":2952,"updated_at":2953,"url":2954,"score":2955},"Current data is wrong. Values are just NULL\r\n\r\nhttps://ve.dolarapi.com/v1/dolares/paralelo\r\n\r\nResponse:\r\n```JSON\r\n{\r\n\"fuente\": \"paralelo\",\r\n\"nombre\": \"Paralelo\",\r\n\"compra\": null,\r\n\"venta\": null,\r\n\"promedio\": 0,\r\n\"fechaActualizacion\": \"2024-10-18T14:00:33.505Z\"\r\n}\r\n```",[2948],{"name":2949,"color":2950},"venezuela","3FB1EC",30,"VE paralelo responds null","2024-10-19T02:46:03Z","https://github.com/enzonotario/esjs-dolar-api/issues/30",0.8345214,{"description":2957,"labels":2958,"number":2960,"owner":2867,"repository":2884,"state":2869,"title":2961,"updated_at":2962,"url":2963,"score":2964},"So, hvaing this in the front matter\r\n\r\n```\r\naside: true\r\noutline: true\r\n``` \r\n\r\nout of the box results in a very verbose set of headings.\r\n\r\nIt might be nice for the default heading levels (or tags used) to present themselves a little nicer in the asied outline!\r\n\r\n\r\n",[2959],{"name":2881,"color":2882},37,"Allow choosing component heading levels","2024-09-19T22:35:35Z","https://github.com/enzonotario/vitepress-openapi/issues/37",0.83735275,["Reactive",2966],{},["Set"],["ShallowReactive",2969],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmJZz3L4XggydstQmxrduoYKyeha3WHsynJPVN0ZQX6g":-1},"/enzonotario/esjs-argentina-datos-api/5"]