\n\nthe postman request:\n\u003Cimg width=\"1356\" height=\"550\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d8f101f6-ff4f-4106-bd8f-016970e70c1e\" />\n\n\u003Cimg width=\"1091\" height=\"691\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/92855ba7-fb6c-4526-8db2-5698519cd093\" />\n\n\n\n2、When I call the download file interface, the \"download files\" button is not responding。\n\n\u003Cimg width=\"392\" height=\"274\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/05b06400-49b1-4885-a710-27fc7be3c34e\" />",[],279,"enzonotario","vitepress-openapi","open","upload and download issues","2025-07-24T13:26:47Z","https://github.com/enzonotario/vitepress-openapi/issues/279",0.7420552,{"description":3027,"labels":3028,"number":3029,"owner":3019,"repository":3020,"state":3021,"title":3030,"updated_at":3031,"url":3032,"score":3033},"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.75740063,{"description":3035,"labels":3036,"number":3037,"owner":3019,"repository":3020,"state":3021,"title":3038,"updated_at":3039,"url":3040,"score":3041},"### Current behavior\n\n`isDark` is not working when using `apparance: 'force-dark'`\n\n### Desired behavior\n\n`isDark = true` when using `apparance: 'force-dark'`\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nSet `apparance: 'force-dark'` in `.vitepress/config.js`\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\nIt's because we are now trying to get `isDark` from the `useData` VitePress composable. However there is a pending issue for this: https://github.com/vuejs/vitepress/pull/4509\n\nDue to this, we are currently retrieving `isDark` from `@vueuse/core`, but it doesn't work when using `apparance: 'force-dark'`.\n\nA workaround would be to allow forcing `isDark` prop from Feature Components.",[],178,"`isDark` is not working when using `apparance: 'force-dark'`","2025-02-17T02:26:34Z","https://github.com/enzonotario/vitepress-openapi/issues/178",0.82566607,{"description":3043,"labels":3044,"number":93,"owner":3019,"repository":3045,"state":3046,"title":3047,"updated_at":3048,"url":3049,"score":3050},"In the file upload scenario, the --header Content-Type does not have a boundary parameter;\nWhen downloading files, the \"download files\" button is not responding\n\n\u003Cimg width=\"522\" height=\"448\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ac3e96e3-4381-4fc4-9785-ba1841730101\" />\n",[],"vitepress-openapi-starter","closed","File upload and download issues","2025-07-24T12:20:31Z","https://github.com/enzonotario/vitepress-openapi-starter/issues/1",0.7373113,{"description":3052,"labels":3053,"number":3057,"owner":3019,"repository":3020,"state":3046,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Current behavior\n\n\n\n### Desired behavior\n\nEither the text should wrap, or just be displayed in a better way\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\n \"securitySchemes\": {\n \"ApiKeyAuth\": {\n \"in\": \"header\",\n \"name\": \"Authorization\",\n \"type\": \"apiKey\",\n\"description\": \"API Key for authentication. Retrieval from either API version login routes, or other authentication token type. See \u003Ca href='/apis/authentication'>Authentication\u003C/a> for more details.\",\n\"example\": \"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOjEsImlhdCI6MTY3Mjc2NjAyOCwiZXhwIjoxNjc0NDk0MDI4fQ.kCak9sLJr74frSRVQp0_27BY4iBCgQSmoT3vQVWKzJg\"\n }\n }\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3054],{"name":3055,"color":3056},"bug","d73a4a",236,"Long Authorization example doesnt display nicely","2025-06-22T12:55:43Z","https://github.com/enzonotario/vitepress-openapi/issues/236",0.76486987,{"description":3063,"labels":3064,"number":3068,"owner":3019,"repository":3020,"state":3046,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### 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_",[3065],{"name":3066,"color":3067},"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.77728057,{"description":3074,"labels":3075,"number":3076,"owner":3019,"repository":3020,"state":3046,"title":3077,"updated_at":3078,"url":3079,"score":3080},"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.78186303,{"description":3082,"labels":3083,"number":3085,"owner":3019,"repository":3020,"state":3046,"title":3086,"updated_at":3087,"url":3088,"score":3089},"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```",[3084],{"name":3066,"color":3067},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.79620457,{"description":3091,"labels":3092,"number":3094,"owner":3019,"repository":3020,"state":3046,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Current behavior\n\nWhen i have the following JSON \n`{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"API with X-Api-Key Authentication\",\n \"version\": \"1.0.0\"\n },\n \"components\": {\n \"securitySchemes\": {\n \"ApiKeyAuth\": {\n \"type\": \"apiKey\",\n \"in\": \"header\",\n \"name\": \"X-Api-Key\"\n }\n }\n },\n \"paths\": {\n \"/protected-endpoint\": {\n \"get\": {\n \"summary\": \"An endpoint requiring X-Api-Key\",\n \"security\": [\n {\n \"ApiKeyAuth\": []\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"401\": {\n \"description\": \"Unauthorized\"\n }\n }\n }\n }\n }\n}`\n\nit shows \n\n\nIn the samples.\n\n### Desired behavior\n\n\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nhttps://docs.xs2event.com/operations/bookings_get.html\n\nhttps://docs.xs2event.com/assets/openapi.json\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3093],{"name":3055,"color":3056},168,"Headers are passed wrong to Samples","2025-02-03T01:59:38Z","https://github.com/enzonotario/vitepress-openapi/issues/168",0.7971944,{"description":3100,"labels":3101,"number":3103,"owner":3019,"repository":3020,"state":3046,"title":3104,"updated_at":3105,"url":3106,"score":3107},"Follow on to https://github.com/enzonotario/vitepress-theme-openapi/issues/10\r\n\r\nIt would be great to allow trying out requests that have a body required.\r\n\r\nProbably a first version of this would just provide a single text input box for the whole \"body\" to be provided.\r\n\r\nUsers could then easily copy and paste the example (probably json) body, and modify it",[3102],{"name":3066,"color":3067},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.8118231,["Reactive",3109],{},["Set"],["ShallowReactive",3112],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMVTHgBBY5L8q20uEXxjQgAzTh-1E1ltovvNIS48hR1g":-1},"/enzonotario/vitepress-openapi/227"]