\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.8285024,{"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.840307,{"description":3035,"labels":3036,"number":3040,"owner":3019,"repository":3020,"state":3041,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### 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_",[3037],{"name":3038,"color":3039},"enhancement","a2eeef",222,"closed","Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.72277033,{"description":3047,"labels":3048,"number":3050,"owner":3019,"repository":3020,"state":3041,"title":3051,"updated_at":3052,"url":3053,"score":3054},"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",[3049],{"name":3038,"color":3039},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.810015,{"description":3056,"labels":3057,"number":3061,"owner":3019,"repository":3020,"state":3041,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### What would you like?\n\nWould it be possible to have a loading indicator for the content?\n\n### Why is this needed?\n\nWhen a user clicks the API button on my documentation, nothing happens for a second or two while the content loads, then the page changes to show the API content.\n\nThis may be related to #171.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3058],{"name":3059,"color":3060},"needs reproduction","ffffff",241,"Loading indicator","2025-06-30T01:30:42Z","https://github.com/enzonotario/vitepress-openapi/issues/241",0.8140319,{"description":3067,"labels":3068,"number":93,"owner":3019,"repository":3069,"state":3041,"title":3070,"updated_at":3071,"url":3072,"score":3073},"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","File upload and download issues","2025-07-24T12:20:31Z","https://github.com/enzonotario/vitepress-openapi-starter/issues/1",0.81825304,{"description":3075,"labels":3076,"number":1337,"owner":3019,"repository":3080,"state":3041,"title":3081,"updated_at":3082,"url":3083,"score":3084},"# Agregar Aplicación a la lista de aplicaciones que consumen ArgentinaDatos.com\r\n\r\n## Información de la Aplicación\r\n\r\n- **Nombre de la Aplicación:**\r\n MERC's Harvey Bot\r\n\r\n- **URL de la Aplicación:**\r\n https://t.me/mercsharvey_bot\r\n\r\n- **Descripción de la Aplicación:**\r\n Bot de Telegram para consultar datos del mercado de valores en Argentina.\r\n",[3077],{"name":3078,"color":3079},"documentation","0075ca","esjs-argentina-datos-api","Listar Aplicación","2024-03-15T02:07:47Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/4",0.8184631,{"description":3086,"labels":3087,"number":734,"owner":3019,"repository":3092,"state":3041,"title":3093,"updated_at":3094,"url":3095,"score":3096},"",[3088,3089],{"name":3038,"color":3039},{"name":3090,"color":3091},"good first issue","7057ff","senadores","Footer con link a argentina datos y al repo open source","2025-02-22T14:02:09Z","https://github.com/enzonotario/senadores/issues/2",0.82411724,{"description":3098,"labels":3099,"number":3103,"owner":3019,"repository":3020,"state":3041,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### 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_",[3100],{"name":3101,"color":3102},"question","d876e3",229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.82506436,{"description":3086,"labels":3109,"number":1337,"owner":3019,"repository":3110,"state":3041,"title":3111,"updated_at":3112,"url":3113,"score":3114},[],"lighthouse-laravel-websockets","It would be nice if there's a readme for how this repo was setup","2020-04-04T01:06:07Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/4",0.8263265,["Reactive",3116],{},["Set"],["ShallowReactive",3119],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fG4StibmDpXmAcbfmBNULFA7JHl6UXO1Ufn7sfr210M4":-1},"/enzonotario/vitepress-openapi/231"]