\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.8474414,{"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\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_",[3182],{"name":3183,"color":3184},"enhancement","a2eeef",204,"closed","support openapi yml file","2025-04-19T22:22:53Z","https://github.com/enzonotario/vitepress-openapi/issues/204",0.82346416,{"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?\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!",[3194],{"name":3183,"color":3184},141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.8276264,{"description":3201,"labels":3202,"number":3203,"owner":3172,"repository":3173,"state":3186,"title":3204,"updated_at":3205,"url":3206,"score":3207},"Hi! I was working on my current project, where I have a schema that produces this UI:\n\nhttps://github.com/user-attachments/assets/21f90ff1-fb58-4aff-86e5-249e453c829f\n\nThis little screencast aims to show that it's a bit non-obvious - especially for people who are just starting to explore the site with the spec and don't know how the UI works - that object properties are there. Long description with some markdown/emojis makes it seem like the description is all that exists under this property.\n\nIn contrast, when there's no description, it's pretty obvious that the properties are expandable:\n\n\u003Cimg width=\"390\" height=\"113\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5b945a5a-e471-44b3-8f18-0e0219c8caa0\" />\n\nBut in the case of a rich description - which is visible by default and draws attention away from the relatively small \"expand\" button icon on the top - a user who reads the description might reasonably assume that it's the only content. They may not think, \"Hmm, I read the description, but there must be properties - let me look for some element that will let me show them!\"\n\n## Suggestions:\n\n### Option 1:\n\nHide descriptions for objects when in Collapsed state, show only when Expanded:\n\nhttps://github.com/user-attachments/assets/40ead49f-6023-4cbb-9a7b-8e5a5c96b952\n\n### Option 2:\n\nShow a small hint after the description, like a verbose \"Expand\" text button or a similar UI element (only shown when it's an array/object and has a description):\n\nhttps://github.com/user-attachments/assets/c8a31a05-6b54-400d-84a9-b126b9762b1e\n\n---\n\nLet me know what you think, @enzonotario! Do you like any of the proposed options, or do you have some other idea of how to address this?",[],271,"[Discussion] When an object has a description, it's not obvious that its properties are expandable","2025-07-21T01:18:22Z","https://github.com/enzonotario/vitepress-openapi/issues/271",0.83077073,{"description":3209,"labels":3210,"number":1672,"owner":3172,"repository":3211,"state":3186,"title":3212,"updated_at":3213,"url":3214,"score":3215},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],"esjs-dolar-api","H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.83571255,{"description":3217,"labels":3218,"number":3219,"owner":3172,"repository":3173,"state":3186,"title":3220,"updated_at":3221,"url":3222,"score":3223},"Hi! It took me some time to figure out how to prevent vitepress-openapi styles from leaking into `.vp-raw` (`:::raw`) blocks. Consider adding an example to the documentation:\n\n```js\n// docs/postcss.config.mjs\n\nimport { postcssIsolateStyles } from 'vitepress';\n\nexport default {\n plugins: [\n // Make `::: raw` sections be isolated from vitepress-openapi plugin styles\n postcssIsolateStyles({\n includeFiles: [ /vitepress-openapi\\.css/ ], // ← NOT `vitepress-openapi/dist/style.css` (!)\n }),\n ],\n};\n```\n\nThank you for your work!",[],251,"Mention style isolation in documentation","2025-07-05T14:22:04Z","https://github.com/enzonotario/vitepress-openapi/issues/251",0.83673394,{"description":3225,"labels":3226,"number":3227,"owner":3172,"repository":3173,"state":3186,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Current behavior\n\nHello,guys\n\nWhen i use that example about the Pages By operation\n\n```md\n---\naside: false\noutline: false\ntitle: vitepress-openapi\n---\n\n\u003Cscript setup lang=\"ts\">\nimport { useRoute } from 'vitepress'\n\nconst route = useRoute()\n\nconst operationId = route.data.params.operationId\n\u003C/script>\n\n\u003COAOperation :operationId=\"operationId\" />\n\n```\n\n```js\nimport { usePaths } from 'vitepress-openapi'\nimport spec from '../../public/test.json' with {type: 'json'}\n\nexport default {\n paths() {\n return usePaths({ spec })\n .getPathsByVerbs()\n .map(({ operationId, summary }) => {\n return {\n params: {\n operationId,\n pageTitle: `${summary} - vitepress-openapi`,\n },\n }\n })\n },\n}\n```\n\nThe terminal show this error,but i dont understand what it mean\n\n\n\nThe terminal guide me the links https://cn.vite.dev/guide/troubleshooting which is show The CJS build of Vite's Node API is deprecated and will be removed in Vite 6. \n\nHope u give the answer thank u so much\n\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n\n\n### Logs and Error Messages\n\n\n\n### Other Information\n\n_No response_",[],212,"Pages by Operation Example dose not work","2025-04-30T22:18:57Z","https://github.com/enzonotario/vitepress-openapi/issues/212",0.8378321,{"description":3233,"labels":3234,"number":3238,"owner":3172,"repository":3173,"state":3186,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Current behavior\n\nI noticed that in the latest version, after executing onSubmit in OAPlayground.vue, the Content-Type header in the POST request observed in the browser console is incorrectly parsed as: `application/json, application/json`\n\nThis issue causes all POST endpoints to fail.\n\n### Desired behavior\n\nManually correcting the Content-Type header to a valid format resolves the issue:\n\n```\ncurl 'https://stoplight.io/mocks/enzonotario/argentine-rock/122547792/api/v1/artists/1/albums' \\\n -H 'accept: */*' \\\n -H 'accept-language: zh-TW,zh;q=0.9,en-US;q=0.8,en;q=0.7' \\\n -H 'authorization: Bearer Token' \\\n -H 'content-type: application/json' \\\n -H 'origin: https://vitepress-openapi.vercel.app' \\\n -H 'priority: u=1, i' \\\n -H 'referer: https://vitepress-openapi.vercel.app/' \\\n -H 'sec-ch-ua: \"Chromium\";v=\"134\", \"Not:A-Brand\";v=\"24\", \"Microsoft Edge\";v=\"134\"' \\\n -H 'sec-ch-ua-mobile: ?0' \\\n -H 'sec-ch-ua-platform: \"macOS\"' \\\n -H 'sec-fetch-dest: empty' \\\n -H 'sec-fetch-mode: cors' \\\n -H 'sec-fetch-site: cross-site' \\\n -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0' \\\n --data-raw '{\"id\":1,\"name\":\"La Máquina de Hacer Pájaros\",\"year\":1976,\"image\":\"https://cdn.rock-legends.com/photos/la-maquina.jpg\"}'\n```\n\nReturns the expected response:\n```\n{\n \"id\": 1,\n \"name\": \"La Máquina de Hacer Pájaros\",\n \"year\": 1976,\n \"image\": \"https://cdn.rock-legends.com/photos/la-maquina.jpg\"\n}\n```\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nReproduction Steps\n\nThis can be verified by copying the generated cURL request. For example, sending a request via the sandbox at:\nhttps://vitepress-openapi.vercel.app/sandbox/#createArtist\n\nThe generated request:\n```\ncurl 'https://stoplight.io/mocks/enzonotario/argentine-rock/122547792/api/v1/artists/1/albums' \\\n -H 'accept: */*' \\\n -H 'accept-language: zh-TW,zh;q=0.9,en-US;q=0.8,en;q=0.7' \\\n -H 'authorization: Bearer Token' \\\n -H 'content-type: application/json, application/json' \\\n -H 'origin: https://vitepress-openapi.vercel.app' \\\n -H 'priority: u=1, i' \\\n -H 'referer: https://vitepress-openapi.vercel.app/' \\\n -H 'sec-ch-ua: \"Chromium\";v=\"134\", \"Not:A-Brand\";v=\"24\", \"Microsoft Edge\";v=\"134\"' \\\n -H 'sec-ch-ua-mobile: ?0' \\\n -H 'sec-ch-ua-platform: \"macOS\"' \\\n -H 'sec-fetch-dest: empty' \\\n -H 'sec-fetch-mode: cors' \\\n -H 'sec-fetch-site: cross-site' \\\n -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0' \\\n --data-raw '{\"id\":1,\"name\":\"La Máquina de Hacer Pájaros\",\"year\":1976,\"image\":\"https://cdn.rock-legends.com/photos/la-maquina.jpg\"}'\n```\nResults in a 500 Internal Server Error.\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\nEnsure that the Content-Type header is set correctly in POST requests to avoid duplicate values.",[3235],{"name":3236,"color":3237},"bug","d73a4a",192,"Incorrect Content-Type Parsing in POST Requests Causes Guaranteed Failure","2025-04-04T22:07:17Z","https://github.com/enzonotario/vitepress-openapi/issues/192",0.8380306,{"description":3244,"labels":3245,"number":1229,"owner":3172,"repository":3173,"state":3186,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### What would you like?\n\nCurrently, When typing in the search box, no api get shown even if they should match the query\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_",[3246],{"name":3247,"color":3248},"question","d876e3","api should appear in search","2024-11-04T00:50:21Z","https://github.com/enzonotario/vitepress-openapi/issues/115",0.83879316,{"description":3254,"labels":3255,"number":3260,"owner":3172,"repository":3173,"state":3186,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### What would you like?\n\nSet the default request and response shown of a `OAOperation` to _schema_, and also be able to collapse it, since I have some large entities.\n\n### Why is this needed?\n\nMakes large request and responses easier to work with.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3256,3259],{"name":3257,"color":3258},"documentation","0075ca",{"name":3183,"color":3184},174,"[Feature]: Set `OAOperation` default `schema` or `json` and collapsed","2025-02-19T23:14:42Z","https://github.com/enzonotario/vitepress-openapi/issues/174",0.842752,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fm3r1xyqgRjC-sVmz3DcXVo7OFndwAzlc39iVj8nGKCg":-1},"/enzonotario/vitepress-openapi/127"]