\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.82077646,{"description":3188,"labels":3189,"number":93,"owner":3172,"repository":3190,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"Si quieres proponer nuevas APIs para ser documentadas, deja un comentario incluyendo lo siguiente:\n\n- Nombre de la API:\n- Descripción breve:\n- URL del OpenAPI o documentación oficial:",[],"apidocs.ar","Propuestas de nuevas APIs a documentar","2025-08-30T12:25:19Z","https://github.com/enzonotario/apidocs.ar/issues/1",0.828736,{"description":3196,"labels":3197,"number":736,"owner":3172,"repository":3190,"state":3174,"title":3198,"updated_at":3199,"url":3200,"score":3201},"Buenas!\n\nPor mas que se especifica\n> Para su uso puede requerirse autenticación mediante token del tipo JWT.\n\n(https://resultados-electorales.argentina.apidocs.ar/)\n\nNo parece realmente necesitarlo? o es solo para algunos endpoints?\nGracias \u003C3",[],"❓ Auth en API resultados electorales","2025-10-10T23:52:15Z","https://github.com/enzonotario/apidocs.ar/issues/2",0.84713507,{"description":3203,"labels":3204,"number":3208,"owner":3172,"repository":3173,"state":3209,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Current behavior\n\n\n\n### Desired behavior\n\nEither the text should wrap, or just be displayed in a better way\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\n \"securitySchemes\": {\n \"ApiKeyAuth\": {\n \"in\": \"header\",\n \"name\": \"Authorization\",\n \"type\": \"apiKey\",\n\"description\": \"API Key for authentication. Retrieval from either API version login routes, or other authentication token type. See \u003Ca href='/apis/authentication'>Authentication\u003C/a> for more details.\",\n\"example\": \"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOjEsImlhdCI6MTY3Mjc2NjAyOCwiZXhwIjoxNjc0NDk0MDI4fQ.kCak9sLJr74frSRVQp0_27BY4iBCgQSmoT3vQVWKzJg\"\n }\n }\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3205],{"name":3206,"color":3207},"bug","d73a4a",236,"closed","Long Authorization example doesnt display nicely","2025-06-22T12:55:43Z","https://github.com/enzonotario/vitepress-openapi/issues/236",0.7532843,{"description":3215,"labels":3216,"number":3218,"owner":3172,"repository":3173,"state":3209,"title":3219,"updated_at":3220,"url":3221,"score":3222},"My rendered component looks something like this\r\n\r\n\r\n\r\nHowever the define route doesnt require authentication\r\n\r\n```\r\n \"/users/login\": {\r\n \"post\": {\r\n \"description\": \"lalala.\",\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/LoginRequest\"\r\n }\r\n }\r\n },\r\n \"description\": \"Login\",\r\n \"required\": true\r\n },\r\n \"responses\": {\r\n \"200\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/LoginResponse\"\r\n }\r\n }\r\n },\r\n \"description\": \"OK\"\r\n },\r\n },\r\n \"summary\": \"Login\",\r\n \"tags\": [\r\n \"users\"\r\n ]\r\n }\r\n },\r\n```\r\n\r\nOther endpoints do specify it as a requirement\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ],\r\n```\r\n\r\nAnd it is defined as a schema in the spec\r\n\r\n```\r\n \"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"in\": \"header\",\r\n \"name\": \"Authorization\",\r\n \"type\": \"apiKey\"\r\n }\r\n }\r\n```\r\n\r\nBut it should not be rendered by default unless they are deinfed in a top level `security` section\r\n\r\nSee https://swagger.io/docs/specification/authentication/ `Step 2.`",[3217],{"name":3206,"color":3207},36,"securitySchemes should only be applied to routes that require it","2024-09-14T16:10:12Z","https://github.com/enzonotario/vitepress-openapi/issues/36",0.77238595,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3209,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Current behavior\n\nGiven this schema:\n```yaml\nopenapi: 3.1.0\ninfo: \n title: test\n version: '0.1'\npaths:\n /test:\n get:\n parameters:\n - in: query\n name: code\n examples:\n name_1:\n value: parameter_value_1\n name_2:\n value: parameter_value_1\n schema:\n type: string\n examples: \n - schema_value_1\n - schema_value_2\n```\n\nThe ui shows `schema_value_1` prefilled for `code` parameter which is incorrect.\n\n### Desired behavior\n\nFor GUI openapi tools `examples` from parameter object itself should be used.\nSo prefilled value should be `parameter_value_1` and not `schema_value_1`\n\nhttps://editor-next.swagger.io also uses examples from parameter object. OpenAPI specification itself does not mention `examples` under `schema` field since it is json-schema field and not OpenAPI specific field.",[],298,"`examples` field is not populated from parameter object","2025-08-27T11:00:31Z","https://github.com/enzonotario/vitepress-openapi/issues/298",0.78035575,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3209,"title":3235,"updated_at":3236,"url":3237,"score":3238},"1、In the file upload scenario, when the browser initiates a request, the header Content-Type does not contain a boundary parameter; normally, when making a request in Postman with a content-type of multipart/form-data, the boundary parameter is automatically included\nthe openai.json:\n\u003Cimg width=\"568\" height=\"832\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e6ec6b35-60cb-4632-bc8b-63fc1cd7ae19\" />\n\nthe postman request:\n\u003Cimg width=\"1356\" height=\"550\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d8f101f6-ff4f-4106-bd8f-016970e70c1e\" />\n\n\u003Cimg width=\"1091\" height=\"691\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/92855ba7-fb6c-4526-8db2-5698519cd093\" />\n\n\n\n2、When I call the download file interface, the \"download files\" button is not responding。\n\n\u003Cimg width=\"392\" height=\"274\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/05b06400-49b1-4885-a710-27fc7be3c34e\" />",[],279,"upload and download issues","2025-08-12T23:37:59Z","https://github.com/enzonotario/vitepress-openapi/issues/279",0.78077877,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3209,"title":3243,"updated_at":3244,"url":3245,"score":3246},"Tried on 0.0.3-alpha.63, and 0.0.3-alpha.79 (latest release)\n\nI have a header such as this defined\n\n```\n {\n \"description\": \"Optionally provide parameters as a JSON object in this header. If both query params and X-Query overlap, a 400 error is returned.\",\n \"example\": \"{\\\"id\\\":\\\"1\\\"}\",\n \"in\": \"header\",\n \"name\": \"X-Query\",\n \"schema\": {\n \"type\": \"string\"\n }\n }\n```\n\nBut also a param like this\n\n```\n {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"in\": \"query\",\n \"name\": \"id\",\n \"schema\": {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"example\": \"1\",\n \"form\": \"id\",\n \"type\": \"string\"\n }\n },\n```\n\nBoth of these examples are used by the UI component, and provided in the default try it requests.\nHowever this means that the request will always fail, as the examples conflict with each other.\nHowever, I want to be able to provide real examples to both of these...\n\nI think that either\n1) Examples should not be used in the default try it param\n2) There should be an option to disable it?",[],221,"example should not always be used as the default for the UI","2025-05-18T01:43:41Z","https://github.com/enzonotario/vitepress-openapi/issues/221",0.7878118,{"description":3248,"labels":3249,"number":3253,"owner":3172,"repository":3173,"state":3209,"title":3254,"updated_at":3255,"url":3256,"score":3257},"The generated example code looks like this...\n\n```\ncurl 'https://api.foo/v2/devices/%7Bid%7D/tags' \\\n --header 'Authorization: xxx'\n```\n\nHowever really in the UI it would be nicer to look like\n\n```\ncurl 'https://api.foo/v2/devices/{id}/tags' \\\n --header 'Authorization: xxx'\n```",[3250],{"name":3251,"color":3252},"enhancement","a2eeef",223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.7943625,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_ZFV5zzHPlnT2PdtaVrJHGZYzgPcCmGAueiUrEuZbHk":-1},"/enzonotario/vitepress-openapi/294"]