\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.8495523,{"description":3180,"labels":3181,"number":3188,"owner":3172,"repository":3173,"state":3189,"title":3190,"updated_at":3191,"url":3192,"score":3193},"### What would you like?\n\nRight now It generate such page \r\n\r\n\r\nwould like to remove Default on the side and move the table of content to the left\r\n\r\nOr alternatively, if I could change the name and add a description so the left do not feel emptu\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,3185],{"name":3183,"color":3184},"enhancement","a2eeef",{"name":3186,"color":3187},"question","d876e3",109,"closed","Any way to remove default or change the name and add description","2024-11-03T03:36:50Z","https://github.com/enzonotario/vitepress-openapi/issues/109",0.8086284,{"description":3195,"labels":3196,"number":3197,"owner":3172,"repository":3173,"state":3189,"title":3198,"updated_at":3199,"url":3200,"score":3201},"### What would you like?\r\n\r\nFirst of all, thank you for providing this great library!\r\n\r\nIt would be great to show operation parameter descriptions, e.g. \r\n\r\n> _**GetBooks**_\r\n> \r\n> _Parameters_\r\n> **pageIndex**: The number of the page to request. The page starts with the value 0\r\n> **sort**: The field to sort the results by. Prefix by \"-\" to invert the sort.\r\n\r\n### Why is this needed?\r\n\r\nJust the name might not be sufficient for users to understand how to use a certain field. OpenAPI provides the description field for further context.\r\n\r\n### How could it be implemented?\r\n\r\nSince the parameter name, required status, and example are already shown in the \"try-it\" section, it would make sense to show the description there as well.\r\n\r\nAlternatively, parameters could be listed in a section above the response documentation.\r\n\r\n### Other information\r\n\r\nI'd be happy to help with the implementation!",[],102,"Show description field of operation parameters","2024-10-30T19:52:59Z","https://github.com/enzonotario/vitepress-openapi/issues/102",0.81395704,{"description":3203,"labels":3204,"number":3205,"owner":3172,"repository":3173,"state":3189,"title":3206,"updated_at":3207,"url":3208,"score":3209},"Thank you for such tool!\n\nI am considering to start using it but I do not understand how to make parameters collapsible.\nI tried with slots/templates approach but was able only substitute parameters component and not wrap. Since I’m not a Vue guy(more like React) can you please suggest how to achieve such behaviour if it is even possible?\n\nI do not wanna substitute OpenAPI parameters component but just wanna wrap it with something like html detail/summary since there are a lot of parameters in my OpenAPI spec and they take huge amount of space. Thanks in advance 🙏 \n\nI tried like this:\n```tsx\n\u003COAOperation :operationId=\"operationId\">\n \u003Ctemplate #parameters=\"{ parameters, operationId }\">\n \u003Cdetails>\n \u003Csummary>Parameters\u003C/summary>\n \u003COAParameters :parameters=\"parameters\" :operationId=\"operationId\" />\n \u003C/details>\n \u003C/template>\n\u003C/OAOperation>\n```\n\nBut cannot figure out where to import `OAParameters` component from...\nBecause getting error: `Vue warn]: Failed to resolve component: OAParameters`",[],290,"How to make Operation parameters collapsible/expandable?","2025-08-08T16:06:36Z","https://github.com/enzonotario/vitepress-openapi/issues/290",0.8156217,{"description":3211,"labels":3212,"number":3213,"owner":3172,"repository":3173,"state":3189,"title":3214,"updated_at":3215,"url":3216,"score":3217},"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.81714004,{"description":3219,"labels":3220,"number":19,"owner":3172,"repository":3173,"state":3189,"title":3222,"updated_at":3223,"url":3224,"score":3225},"I believe the currentl link prefix is hardcoded `link: `/operations/${c}``\r\n\r\nHowever ultimately I would like to link to 2 different specs under 2 different URL prefixes, such as...\r\n - `http://localhost:5173/apis/v2/`\r\n - `http://localhost:5173/apis/v1/`\r\n\r\nTo do this I guess I would need to pass a prefix into the methods such as `generateSidebarGroup`\r\n\r\nMy current code is:\r\n\r\n```\r\n {\r\n text: 'Version 2',\r\n link: '/apis/v2',\r\n items: [\r\n sidebar.generateSidebarGroup([\"users\", \"published\"],\"Users\"),\r\n ],\r\n },\r\n```",[3221],{"name":3183,"color":3184},"Custom sidebar menu item link","2024-09-18T01:38:40Z","https://github.com/enzonotario/vitepress-openapi/issues/38",0.83189267,{"description":3227,"labels":3228,"number":3230,"owner":3172,"repository":3173,"state":3189,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### What would you like?\n\nHow can I create my own custom components to implement my own needs?\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_",[3229],{"name":3186,"color":3187},229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.8346243,{"description":3236,"labels":3237,"number":3238,"owner":3172,"repository":3239,"state":3189,"title":3240,"updated_at":3241,"url":3242,"score":3243},"Hola buenas tardes estimados, no se esta actualizando el valor del dolar bolsa.",[],44,"esjs-dolar-api","[HOTFIX] Dolar MEP no esta actualizandose","2025-04-16T16:04:37Z","https://github.com/enzonotario/esjs-dolar-api/issues/44",0.8422537,{"description":3245,"labels":3246,"number":3248,"owner":3172,"repository":3173,"state":3189,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### What would you like?\n\nI'd love it if there was an easy to use component that allowed displaying a link that looked like the nice fancy sidebars\n\nThis should be documented\n\n\n\nI'd like to be able to use this anywhere in text\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_",[3247],{"name":3183,"color":3184},222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.8425796,{"description":3254,"labels":3255,"number":3257,"owner":3172,"repository":3173,"state":3189,"title":3258,"updated_at":3259,"url":3260,"score":3261},"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```",[3256],{"name":3183,"color":3184},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.8433853,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7KDd8wMUQ_f3fz4fE-xyKbqVTKQawgKnGzECjd72GGw":-1},"/enzonotario/esjs-dolar-api/29"]