\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.8049018,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3183,"title":3184,"updated_at":3185,"url":3186,"score":3187},"### What would you like?\n\nSwagger-ui has the option to set a token once for the site and have it be used for every test api call. Maybe such an option would also be nice for the openapi theme.\n\n### Why is this needed?\n\nMakes it a bit friendlier to use as you do not need to constantly insert a bearer token.\n\n### How could it be implemented?\n\nSimilarly to how swagger-ui does it. Have a global button which stores the authentication method / value.\n\n### Other information\n\n_No response_",[],59,"closed","[Feature] Site-wide authentication","2024-09-29T13:52:47Z","https://github.com/enzonotario/vitepress-openapi/issues/59",0.7089467,{"description":3189,"labels":3190,"number":3194,"owner":3172,"repository":3173,"state":3183,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### 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_",[3191],{"name":3192,"color":3193},"enhancement","a2eeef",81,"Group operations into tags groups","2024-10-12T13:41:02Z","https://github.com/enzonotario/vitepress-openapi/issues/81",0.74566543,{"description":3200,"labels":3201,"number":3203,"owner":3172,"repository":3173,"state":3183,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### What would you like?\n\nThe current version generates \"static\" code for each language, based only on the url and method. Unfortunately, the url is simply: `const url = props.baseUrl + props.path`. This has the issue that any path parameters are left as-is in the code.\r\n\r\nIt would be great if the sample code could be updated to include the variables in the \"try it\" box. This way the code sample would be \"complete\". I _think_ this would be done in much the same was as the `OACodeBlock` currently computes the URL for curl\n\n### Why is this needed?\n\nIf you copy-and-paste the code sample as-is, you will end up with an invalid URL if there are path parameters.\r\n\r\nAlso, it would be nice to mix-and-match such that you can _remove_ the try it portion of the playground, but keep the sample code. This way people can \"build\" a request in their language of choice based on the variables form.\n\n### How could it be implemented?\n\nI _think_ you would need to extract (or just duplicate?) the code used to compute the curl information:\r\n\r\n```\r\nconst curl = computed(() => {\r\n const headers = request.value.headers\r\n if (!headers?.['Content-Type']) {\r\n headers['Content-Type'] = 'application/json'\r\n }\r\n\r\n return fetchToCurl({\r\n method: props.method.toUpperCase(),\r\n url: request.value.url,\r\n headers,\r\n body: request.value.body ? formatJson(request.value.body) : null,\r\n })\r\n})\r\n```\r\n\r\nThen pass this as a parameter to `generateCodeSamples` so that it can generate each code sample appropriately.\n\n### Other information\n\nIt would also be _awesome_ to select _which_ languages you want to support, and possibly even some way to provide the template for each language. I realize this is above-and-beyond, but something to think about if you're changing this.",[3202],{"name":3192,"color":3193},92,"Modify Sample Code Based on Variables","2024-11-15T02:40:07Z","https://github.com/enzonotario/vitepress-openapi/issues/92",0.77248716,{"description":3209,"labels":3210,"number":3212,"owner":3172,"repository":3173,"state":3183,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### 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_",[3211],{"name":3192,"color":3193},91,"Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.77897656,{"description":3218,"labels":3219,"number":3220,"owner":3172,"repository":3173,"state":3183,"title":3221,"updated_at":3222,"url":3223,"score":3224},"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.78005993,{"description":3226,"labels":3227,"number":3229,"owner":3172,"repository":3173,"state":3183,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### 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",[3228],{"name":3192,"color":3193},131,"Display better response examples for arrays of a schema","2024-12-12T09:25:53Z","https://github.com/enzonotario/vitepress-openapi/issues/131",0.7815651,{"description":3235,"labels":3236,"number":3240,"owner":3172,"repository":3173,"state":3183,"title":3241,"updated_at":3242,"url":3243,"score":3244},"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.",[3237],{"name":3238,"color":3239},"bug","d73a4a",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.7929894,{"description":3246,"labels":3247,"number":3249,"owner":3172,"repository":3173,"state":3183,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Current behavior\n\nin a setup where all operations are sown in one page, the table of content contains links to each one of them as anchor links\r\n\r\nThe operation that have parameters in their url (using`{}`) have their links not working\n\n### Desired behavior\n\nI expect all links to work\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\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# navigate to http://localhost:5173/api-all-in-one/\r\n# click on links\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3248],{"name":3238,"color":3239},108,"anchor links that have parameter do not work","2024-11-06T00:17:01Z","https://github.com/enzonotario/vitepress-openapi/issues/108",0.7998015,{"description":3255,"labels":3256,"number":3260,"owner":3172,"repository":3261,"state":3183,"title":3262,"updated_at":3263,"url":3264,"score":3265},"- **Descripción de la Aplicación:**\n \u003C!-- Proporciona una breve descripción -->",[3257],{"name":3258,"color":3259},"documentation","0075ca",41,"esjs-dolar-api","volokokoti","2025-03-04T12:28:13Z","https://github.com/enzonotario/esjs-dolar-api/issues/41",0.8025036,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fE82KkhC8zKPQzl9HHSUxxpaUwNlTnbcmQewpV_MYEak":-1},"/enzonotario/esjs-dolar-api/40"]