\n\nWhich looks nice, and is copyable in the left-hand side, however the right hand side syas [object Obvject] etc...\n\n---------------\n\nWhen specifying strings of json as the filters like this\n\n```\n 'filter': [\n '{\"limit\":10,\"order\":[\"timestamp DESC\"]}',\n '{\"where\":{\"timestamp\":{\"between\":[\"2024-12-01T00:00:00.000Z\",\"2024-12-01T23:59:59.999Z\"]}},\"order\":[\"timestamp DESC\"]}',\n '{\"where\":{\"correlationId\":\"abc123\"}}',\n ],\n```\n\nWe get an ugly left-hand side with escaping, and a nice right-hand side placeholder (no extra escaping)\n\n\u003Cimg width=\"1509\" height=\"220\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a411efc1-f555-4d69-abb3-0dab9ee25450\" />\n\nUltimately in one of these cases, I would like the left-hand side to have a copyable string without escaping of \", and in the right-hand side it still be shown nicely in the placeholder.",[],301,"enzonotario","vitepress-openapi","open","Consistently handle example json escaping","2025-08-28T15:58:55Z","https://github.com/enzonotario/vitepress-openapi/issues/301",0.82551366,{"description":3180,"labels":3181,"number":3185,"owner":3172,"repository":3173,"state":3186,"title":3187,"updated_at":3188,"url":3189,"score":3190},"### What would you like?\n\nTo be able to define a schema such as the following as a content response\r\n\r\n```\r\n \"schema\": {\r\n \"type\": \"array\",\r\n \"items\": {\r\n \"$ref\": \"#/components/schemas/datapoint\"\r\n }\r\n }\r\n```\r\n\r\nAnd have it display an example using the datapoint schema, rather than just displaying `[]`\n\n### Why is this needed?\n\nMore useful infomation via examples to users.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\nCurrent example just looks like this\r\n\r\n\r\n",[3182],{"name":3183,"color":3184},"enhancement","a2eeef",131,"closed","Display better response examples for arrays of a schema","2024-12-12T09:25:53Z","https://github.com/enzonotario/vitepress-openapi/issues/131",0.76451105,{"description":3192,"labels":3193,"number":3195,"owner":3172,"repository":3173,"state":3186,"title":3196,"updated_at":3197,"url":3198,"score":3199},"### What would you like?\n\nI'd like to be able to render the openapi specification with a signle column layout. It would be nice if it is configurable in the parameters of the components like OASpec or globally in the theme config. In addition to that, it would also be nice if the different child components could be enabled/disabled (i.e. turn off samples). \n\n### Why is this needed?\n\nI want this because the standard theme does not have a lot of content width, Having a two column layout looks crowded and sometimes the content is wrapped. Having all the child components below each other with a single column layout would bring more clarity to the rendered documentation.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3194],{"name":3183,"color":3184},91,"Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.7651404,{"description":3201,"labels":3202,"number":3209,"owner":3172,"repository":3173,"state":3186,"title":3210,"updated_at":3211,"url":3212,"score":3213},"On my site I have the following in my vitepress config\r\n\r\n```\r\n search: {\r\n provider: 'local'\r\n }\r\n```\r\n\r\nper https://vitepress.dev/reference/default-theme-search\r\n\r\nHowever, pages rendered via the method suggested `*.paths.js` doesnt appear in the search.\r\n\r\n\r\n\r\nSeemingly none of the example sites currently include search, and thus the component doesnt appear to work with search?",[3203,3206],{"name":3204,"color":3205},"documentation","0075ca",{"name":3207,"color":3208},"question","d876e3",47,"Working example with search provider local set","2024-09-18T12:40:44Z","https://github.com/enzonotario/vitepress-openapi/issues/47",0.76686835,{"description":3215,"labels":3216,"number":1612,"owner":3172,"repository":3218,"state":3186,"title":3219,"updated_at":3220,"url":3221,"score":3222},"",[3217],{"name":3204,"color":3205},"esjs-dolar-api","Add Dollar Blue for Bolivia","2025-02-17T22:04:29Z","https://github.com/enzonotario/esjs-dolar-api/issues/37",0.7700481,{"description":3224,"labels":3225,"number":3227,"owner":3172,"repository":3173,"state":3186,"title":3228,"updated_at":3229,"url":3230,"score":3231},"Seria interesante que haya una documentación que logre adaptarse al lenguaje seleccionado desde un selector. Ya dependería de uno agregar algún lenguaje adicional en nuestra docs del proyecto. ",[3226],{"name":3183,"color":3184},128,"Multilenguaje ","2024-12-15T03:19:43Z","https://github.com/enzonotario/vitepress-openapi/issues/128",0.7744708,{"description":3233,"labels":3234,"number":1511,"owner":3172,"repository":3173,"state":3186,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### What would you like?\r\n\r\nCurrently, each endpoint can only use 1 securityScheme despite OAS 3 being able to specify multiple securityScheme must be used together \r\nhttps://swagger.io/docs/specification/v3_0/authentication/#using-multiple-authentication-types\r\n\r\nDefining security schemes:\r\n```json\r\n\"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"type\": \"http\",\r\n \"scheme\": \"bearer\",\r\n \"description\": \"API Key\"\r\n },\r\n \"Signature\": {\r\n \"name\": \"x-signature\",\r\n \"type\": \"apiKey\",\r\n \"in\": \"header\",\r\n \"description\": \"Request signature\"\r\n }\r\n },\r\n```\r\n\r\nIn endpoint:\r\n```json\r\n\"security\": [{ \"Signature\": [] }, { \"ApiKeyAuth\": [] }],\r\n```\r\n\r\n### Why is this needed?\r\n\r\nWhen allowing user to test the endpoints, if the API requires 2+ security schemes to be used together, the try it would not able to show 2 security fields\r\n\r\n\r\n\r\n### How could it be implemented?\r\n\r\nUpdating OASecurity and OATryWithVariables\r\n\r\n### Other information\r\n\r\nExample implementation from [Scalar](https://github.com/scalar/scalar):\r\n\r\n",[3235],{"name":3183,"color":3184},"Support multiple security together when specified","2024-12-21T01:50:26Z","https://github.com/enzonotario/vitepress-openapi/issues/129",0.78377795,{"description":3241,"labels":3242,"number":3244,"owner":3172,"repository":3173,"state":3186,"title":3245,"updated_at":3246,"url":3247,"score":3248},"### What would you like?\n\nWhen operations with different tags are rendered on the same page, they should be grouped by tags, as it happens in Swagger.\r\n\r\n\n\n### Why is this needed?\n\n_No response_\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3243],{"name":3183,"color":3184},81,"Group operations into tags groups","2024-10-12T13:41:02Z","https://github.com/enzonotario/vitepress-openapi/issues/81",0.7961971,{"description":3250,"labels":3251,"number":3253,"owner":3172,"repository":3218,"state":3186,"title":3254,"updated_at":3255,"url":3256,"score":3257},"# Agregar Aplicación a la lista de aplicaciones que consumen DolarApi.com\n\n## Información de la Aplicación\n\n- **Nombre de la Aplicación:**\n Dólar Ahora\n\n- **URL de la Aplicación:**\n https://play.google.com/store/apps/details?id=com.fraancogaalfras.dolarahora\n\n- **Descripción de la Aplicación:**\n App móvil para consultar el precio de los dólares financieros en Argentina.\n",[3252],{"name":3204,"color":3205},39,"Listar Aplicación - Dólar Ahora","2025-03-01T20:46:40Z","https://github.com/enzonotario/esjs-dolar-api/issues/39",0.8014315,{"description":3259,"labels":3260,"number":3262,"owner":3172,"repository":3173,"state":3186,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### What would you like?\r\n\r\nIt would be nice to have a select element that switches between request body examples.\r\nThis is possible in swagger UI, for example:\r\n\r\n\u003Cimg width=\"1672\" alt=\"Screenshot 2024-12-27 at 15 12 50\" src=\"https://github.com/user-attachments/assets/e5313373-cc8f-4027-9311-0e5d446b6027\" />\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!",[3261],{"name":3183,"color":3184},141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.8156091,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKMOMnOJCkFAi10Ho7wuPQiAPEqVYi4kwY2rcwS9ttso":-1},"/enzonotario/vitepress-openapi/163"]