\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,"Consistently handle example json escaping","2025-08-28T15:58:55Z","https://github.com/enzonotario/vitepress-openapi/issues/301",0.8268516,{"description":3188,"labels":3189,"number":93,"owner":3172,"repository":3190,"state":3191,"title":3192,"updated_at":3193,"url":3194,"score":3195},"In the file upload scenario, the --header Content-Type does not have a boundary parameter;\nWhen downloading files, the \"download files\" button is not responding\n\n\u003Cimg width=\"522\" height=\"448\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ac3e96e3-4381-4fc4-9785-ba1841730101\" />\n",[],"vitepress-openapi-starter","closed","File upload and download issues","2025-07-24T12:20:31Z","https://github.com/enzonotario/vitepress-openapi-starter/issues/1",0.5413692,{"description":3197,"labels":3198,"number":3199,"owner":3172,"repository":3173,"state":3191,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### What would you like?\n\nThis is what I expect.\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_",[],227,"Is the application/x-www-form-urlencoded content type supported?","2025-05-29T23:41:20Z","https://github.com/enzonotario/vitepress-openapi/issues/227",0.7601078,{"description":3205,"labels":3206,"number":3207,"owner":3172,"repository":3173,"state":3191,"title":3208,"updated_at":3209,"url":3210,"score":3211},"### Current behavior\n\nMy security scheme is as follows:\n`\"securitySchemes\": {\n \"APIKeyQuery\": {\n \"type\": \"apiKey\",\n \"in\": \"query\",\n \"name\": \"api_key\"\n }`\n\nWhen clicking \"Try it out\", the browser sends:\n```\nGET /api/endpoint\nHeaders: Api_key: example_key\n```\n\n### Desired behavior\n\n`GET /api/endpoint?api_key=example_key`\n\n### Steps to reproduce\n**Environment:**\n- vitepress-openapi@0.1.7\n- \"vitepress\": \"^1.6.3\"\n- browser: any\n\nadd `\"securitySchemes\": {\n \"APIKeyQuery\": {\n \"type\": \"apiKey\",\n \"in\": \"query\",\n \"name\": \"api_key\"\n }` to your openapi.json\nand see that it goes to headers instead of query\n\n### Logs and Error Messages\n\nThis causes API calls to fail since our server expects the API key as a query parameter, making the interactive documentation unusable.\n\n### Other Information\n\nCan you please fix this?",[],294,"API key query parameters sent as headers instead","2025-08-13T01:15:02Z","https://github.com/enzonotario/vitepress-openapi/issues/294",0.77978593,{"description":3213,"labels":3214,"number":3218,"owner":3172,"repository":3219,"state":3191,"title":3220,"updated_at":3221,"url":3222,"score":3223},"Hola buenos dias estimados queria consultarles el horario de actualizacion que tienen para el Dolar Bolsa para no realizar requests de más. Desde ya muchas gracias",[3215],{"name":3216,"color":3217},"question","d876e3",42,"esjs-dolar-api","Consulta horarios de actualizacion","2025-03-20T18:46:11Z","https://github.com/enzonotario/esjs-dolar-api/issues/42",0.79322755,{"description":3225,"labels":3226,"number":3230,"owner":3172,"repository":3173,"state":3191,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### What would you like?\n\nsupport openapi yml file\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_",[3227],{"name":3228,"color":3229},"enhancement","a2eeef",204,"support openapi yml file","2025-04-19T22:22:53Z","https://github.com/enzonotario/vitepress-openapi/issues/204",0.7995664,{"description":3236,"labels":3237,"number":3238,"owner":3172,"repository":3173,"state":3191,"title":3239,"updated_at":3240,"url":3241,"score":3242},"I noticed this while playing with the auth tokens, however it probably applies to all fields.\n\nIt would be really nice while clicking into a field that has `.` chars in it, if by default it would select the whole field?\n\n\n\nFor this token, it breaks on the 2 `.` sections",[],247,"Change field selection boundaries","2025-06-26T22:32:02Z","https://github.com/enzonotario/vitepress-openapi/issues/247",0.8009302,{"description":3244,"labels":3245,"number":3218,"owner":3172,"repository":3173,"state":3191,"title":3247,"updated_at":3248,"url":3249,"score":3250},"Follow on to https://github.com/enzonotario/vitepress-theme-openapi/issues/10\r\n\r\nIt would be great to allow trying out requests that have a body required.\r\n\r\nProbably a first version of this would just provide a single text input box for the whole \"body\" to be provided.\r\n\r\nUsers could then easily copy and paste the example (probably json) body, and modify it",[3246],{"name":3228,"color":3229},"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.81234163,{"description":3252,"labels":3253,"number":3255,"owner":3172,"repository":3173,"state":3191,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### Current behavior\r\n\r\nMy openapi spec contains oneOf and prefixItems \r\n\r\n- [x] #124\r\n\r\n- [x] #125\r\n\r\n### Desired behavior\r\n\r\n_No response_\r\n\r\n### Reproduction\r\n\r\n_No response_\r\n\r\n### Steps to reproduce\r\n\r\n```\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:dev\r\n# for oneOf, see http://localhost:5173/api-all-in-one/#get-api-paymentAccountBroadcaster\r\n# it shows null, while null is only one of the possible type\r\n\r\n# for prefixItems I had an earlier example here : https://github.com/wighawag/fuzd/commit/d47b3452280a13aeb6d38c6c7301e51b8be7f2fc\r\n# where error (click 500) where not showing properly because I was using prefixItems\r\n```\r\n\r\n### Logs and Error Messages\r\n\r\n_No response_\r\n\r\n### Other Information\r\n\r\n_No response_",[3254],{"name":3228,"color":3229},111,"prefixItems and oneOf does not seems to be supported","2025-05-03T22:18:47Z","https://github.com/enzonotario/vitepress-openapi/issues/111",0.8259603,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUvy2pbPE8XSSHBnJcDswPTCdmDdMy9WpKaGpL3_bHk4":-1},"/enzonotario/vitepress-openapi/279"]