\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.7939807,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3191,"title":3192,"updated_at":3193,"url":3194,"score":3195},"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,"closed","How to make Operation parameters collapsible/expandable?","2025-08-08T16:06:36Z","https://github.com/enzonotario/vitepress-openapi/issues/290",0.761989,{"description":3197,"labels":3198,"number":3202,"owner":3172,"repository":3173,"state":3191,"title":3203,"updated_at":3204,"url":3205,"score":3206},"### 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_",[3199],{"name":3200,"color":3201},"enhancement","a2eeef",222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.7641366,{"description":3208,"labels":3209,"number":3210,"owner":3172,"repository":3173,"state":3191,"title":3211,"updated_at":3212,"url":3213,"score":3214},"I believe spec such as this is valid and OK.\n\nBasically having a schema object, that has a property of type string, and then using oneOf to be abe to define extra information about the strings.\n\n```\n \"notificationTrigger\": {\n \"properties\": {\n \"name\": {\n \"type\": \"string\"\n },\n \"type\": {\n \"type\": \"string\",\n \"oneOf\": [\n { \"const\": \"lowBat\", \"title\": \"Low Battery\", \"description\": \"Triggered when battery level is low.\" },\n { \"const\": \"button\", \"title\": \"Button Press\", \"description\": \"Triggered on a button press.\" },\n \n```\n\nI believe a relevant link from the spec would be https://spec.openapis.org/oas/v3.1.1.html#model-with-annotated-enumeration\n\nHowever the components currently render this incorrectly.\n\n\u003Cimg width=\"670\" height=\"396\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/267cff6d-9c0a-4bd7-8a8e-734588fb775b\" />",[],288,"Support rendering model-with-annotated-enumeration in Request Body schema","2025-08-11T22:29:43Z","https://github.com/enzonotario/vitepress-openapi/issues/288",0.78315765,{"description":3216,"labels":3217,"number":3218,"owner":3172,"repository":3173,"state":3191,"title":3219,"updated_at":3220,"url":3221,"score":3222},"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.79478353,{"description":3224,"labels":3225,"number":1612,"owner":3172,"repository":3173,"state":3191,"title":3227,"updated_at":3228,"url":3229,"score":3230},"So, hvaing this in the front matter\r\n\r\n```\r\naside: true\r\noutline: true\r\n``` \r\n\r\nout of the box results in a very verbose set of headings.\r\n\r\nIt might be nice for the default heading levels (or tags used) to present themselves a little nicer in the asied outline!\r\n\r\n\r\n",[3226],{"name":3200,"color":3201},"Allow choosing component heading levels","2024-09-19T22:35:35Z","https://github.com/enzonotario/vitepress-openapi/issues/37",0.7970981,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3191,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### 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.7999188,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3191,"title":3243,"updated_at":3244,"url":3245,"score":3246},"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.80090654,{"description":3248,"labels":3249,"number":3251,"owner":3172,"repository":3173,"state":3191,"title":3252,"updated_at":3253,"url":3254,"score":3255},"### 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_",[3250],{"name":3200,"color":3201},91,"Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.80093354,["Reactive",3257],{},["Set"],["ShallowReactive",3260],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmwbWxhYJtbEyx_IWWKFJxJONMYDEGLmclpqflvxMKOQ":-1},"/enzonotario/vitepress-openapi/271"]