\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.77647716,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"So, following on from https://github.com/enzonotario/vitepress-openapi/issues/237#issuecomment-2994204686\n\nThis \"issue\" is rather a place to collect my thoughts and discuss, potentially some of these ideas are bad, but its the combination of thoughts given the `xxx` confusion I had, + pulling in thoughts from other tooling I have used.\n\n---\n\n\n\nThe display of `xxx` is unclear to me in terms of what it is trying to communicate.\nIt could be one of these things\n - xxx is the example, a placeholder for you to enter something into\n - It could be representing the fact that a value is there, but we dont want to show you (like `***` for passwords)\n - It could be the actual value saved in local storage? waiting for you to update it?\n\nWhen loading first time and making a request, I actually saw that it made a request with a literal `xxx`\n\n\n\nNot sure if this is something I had entered though?\n\nIt was indeed stored in local storage (and the UI didn't really help me figure that out...)\n\n\n\nDeleting the key from local storage, and I then correctly see the example appear in the latest version\n\n\n\nAs a result, im not sure if https://github.com/enzonotario/vitepress-openapi/issues/237 even was an issue, or rather just I had no idea where the `xxx` was coming from?\n\nSo, I would propose......\n\n**1)When key is stored and coming form local storage, keep it editable**\n\nCurrently when its coming form local storage, it is the placeholder for the field..\n\n\n\nThis makes it appear exactly like the example, and examples else where and thus is easily confused.\n\nI see other API sandboxes just keep / load the field into the text box and leave it there, so perhaps just do that?\n\n**2)Hover text for field saying it is stored between sessions in local storage?**\n\nAgain, a subtle way to make it easier for folks to understand what it going on?\n\n**3)Provide a way to clear from local storage**\n\nPerhaps a small clear button next to the APIKey name?\n\n\n\nMaybe there should even be a save button here rather than doing it automatically?\n\nPerhaps all of what I have said and am saying should be other in the other component?\n\n\n\n**4) Provide an optional button next to token field, to take a user to a page to setup the api key?**\n\nThis could be a custom dedicated page with custom content.\nIt thus could be as simple as just a page with instructions, and also a text box and save button that would put the key in local storage?\nIt could also just be a popup?\n\nPerhaps a default component for use on such as page could be used that takes the key and puts it in the right place in local storage?\n\nAnd perhaps another way of default option that could be provided would be a link to the route page that would generate the token, such as in my case http://localhost:8093/apis/v2/post-users-login\nOnce making the request and getting a response, next to the response would be a button to say \"set as API key\" or such?\nSo this would require some additional options on the route component?\n\nPerhaps something in one of these 3 green places?\n\n",[],246,"Ideas around Authorization saving and population","2025-06-23T08:01:09Z","https://github.com/enzonotario/vitepress-openapi/issues/246",0.7892781,{"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.8411129,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3199,"title":3200,"updated_at":3201,"url":3202,"score":3203},"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,"closed","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.6928614,{"description":3205,"labels":3206,"number":3207,"owner":3172,"repository":3173,"state":3199,"title":3208,"updated_at":3209,"url":3210,"score":3211},"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.7833219,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3199,"title":3216,"updated_at":3217,"url":3218,"score":3219},"### Current behavior\n\nMy security scheme is as follows:\n`\"securitySchemes\": {\n \"APIKeyQuery\": {\n \"type\": \"apiKey\",\n \"in\": \"query\",\n \"name\": \"api_key\"\n }`\n\nWhen clicking \"Try it out\", the browser sends:\n```\nGET /api/endpoint\nHeaders: Api_key: example_key\n```\n\n### Desired behavior\n\n`GET /api/endpoint?api_key=example_key`\n\n### Steps to reproduce\n**Environment:**\n- vitepress-openapi@0.1.7\n- \"vitepress\": \"^1.6.3\"\n- browser: any\n\nadd `\"securitySchemes\": {\n \"APIKeyQuery\": {\n \"type\": \"apiKey\",\n \"in\": \"query\",\n \"name\": \"api_key\"\n }` to your openapi.json\nand see that it goes to headers instead of query\n\n### Logs and Error Messages\n\nThis causes API calls to fail since our server expects the API key as a query parameter, making the interactive documentation unusable.\n\n### Other Information\n\nCan you please fix this?",[],294,"API key query parameters sent as headers instead","2025-08-13T01:15:02Z","https://github.com/enzonotario/vitepress-openapi/issues/294",0.7848706,{"description":3221,"labels":3222,"number":3229,"owner":3172,"repository":3173,"state":3199,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### 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_",[3223,3226],{"name":3224,"color":3225},"enhancement","a2eeef",{"name":3227,"color":3228},"question","d876e3",109,"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.7907417,{"description":3235,"labels":3236,"number":3238,"owner":3172,"repository":3173,"state":3199,"title":3239,"updated_at":3240,"url":3241,"score":3242},"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```",[3237],{"name":3224,"color":3225},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.80423963,{"description":3244,"labels":3245,"number":3247,"owner":3172,"repository":3173,"state":3199,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Current behavior\r\n\r\nMy openapi spec contains oneOf and prefixItems \r\n\r\n- [x] #124\r\n\r\n- [x] #125\r\n\r\n### Desired behavior\r\n\r\n_No response_\r\n\r\n### Reproduction\r\n\r\n_No response_\r\n\r\n### Steps to reproduce\r\n\r\n```\r\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# for oneOf, see http://localhost:5173/api-all-in-one/#get-api-paymentAccountBroadcaster\r\n# it shows null, while null is only one of the possible type\r\n\r\n# for prefixItems I had an earlier example here : https://github.com/wighawag/fuzd/commit/d47b3452280a13aeb6d38c6c7301e51b8be7f2fc\r\n# where error (click 500) where not showing properly because I was using prefixItems\r\n```\r\n\r\n### Logs and Error Messages\r\n\r\n_No response_\r\n\r\n### Other Information\r\n\r\n_No response_",[3246],{"name":3224,"color":3225},111,"prefixItems and oneOf does not seems to be supported","2025-05-03T22:18:47Z","https://github.com/enzonotario/vitepress-openapi/issues/111",0.8081498,{"description":3253,"labels":3254,"number":3255,"owner":3172,"repository":3173,"state":3199,"title":3256,"updated_at":3257,"url":3258,"score":3259},"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.8087544,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPkTXiVsIEluItinogkEjb5a_KhqRg_ltW2M2b37ZIyE":-1},"/enzonotario/vitepress-openapi/298"]