\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.5394556,{"description":3028,"labels":3029,"number":3030,"owner":3020,"repository":3021,"state":3022,"title":3031,"updated_at":3032,"url":3033,"score":3034},"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.81448805,{"description":3036,"labels":3037,"number":3038,"owner":3020,"repository":3021,"state":3039,"title":3040,"updated_at":3041,"url":3042,"score":3043},"### 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,"closed","Is the application/x-www-form-urlencoded content type supported?","2025-05-29T23:41:20Z","https://github.com/enzonotario/vitepress-openapi/issues/227",0.7402239,{"description":3045,"labels":3046,"number":3050,"owner":3020,"repository":3051,"state":3039,"title":3052,"updated_at":3053,"url":3054,"score":3055},"Hola buenos dias estimados queria consultarles el horario de actualizacion que tienen para el Dolar Bolsa para no realizar requests de más. Desde ya muchas gracias",[3047],{"name":3048,"color":3049},"question","d876e3",42,"esjs-dolar-api","Consulta horarios de actualizacion","2025-03-20T18:46:11Z","https://github.com/enzonotario/esjs-dolar-api/issues/42",0.7755473,{"description":3057,"labels":3058,"number":3062,"owner":3020,"repository":3021,"state":3039,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### What would you like?\n\nsupport openapi yml file\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_",[3059],{"name":3060,"color":3061},"enhancement","a2eeef",204,"support openapi yml file","2025-04-19T22:22:53Z","https://github.com/enzonotario/vitepress-openapi/issues/204",0.8031057,{"description":3068,"labels":3069,"number":3070,"owner":3020,"repository":3021,"state":3039,"title":3071,"updated_at":3072,"url":3073,"score":3074},"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.81308097,{"description":3076,"labels":3077,"number":3081,"owner":3020,"repository":3021,"state":3039,"title":3082,"updated_at":3083,"url":3084,"score":3085},"Take the following minimal crashable example:\r\n\r\n```json\r\n{\r\n \"openapi\": \"3.0.0\",\r\n \"info\": {\r\n \"title\": \"Minimal API with Circular Reference\",\r\n \"version\": \"1.0.0\"\r\n },\r\n \"paths\": {\r\n \"/parent\": {\r\n \"get\": {\r\n \"summary\": \"Get a parent\",\r\n \"operationId\": \"getParent\",\r\n \"responses\": {\r\n \"200\": {\r\n \"description\": \"A parent with a child\",\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/Parent\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"components\": {\r\n \"schemas\": {\r\n \"Parent\": {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"string\"\r\n },\r\n \"child\": {\r\n \"$ref\": \"#/components/schemas/Child\"\r\n }\r\n }\r\n },\r\n \"Child\": {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"string\"\r\n },\r\n \"parent\": {\r\n \"$ref\": \"#/components/schemas/Parent\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\nThis is valid openapi spec as can be seen checked using a [validator](https://apitools.dev/swagger-parser/online/). Of course, dealing with a circular swagger requires a form of normalization. \r\n\r\nI am currently using the standard swagger UI, which does nicely deal with circular references. However, as I have moved all my documentation over to vitepress, I would also prefer to maybe include some swagger here and there as it could help make explanations a bit clearer.",[3078],{"name":3079,"color":3080},"bug","d73a4a",57,"[BUG] Generator crashes if openapi-spec contains a circular reference","2024-09-28T15:43:59Z","https://github.com/enzonotario/vitepress-openapi/issues/57",0.8187935,{"description":3087,"labels":3088,"number":734,"owner":3020,"repository":3093,"state":3039,"title":3094,"updated_at":3095,"url":3096,"score":3097},"",[3089,3090],{"name":3060,"color":3061},{"name":3091,"color":3092},"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.8207347,{"description":3099,"labels":3100,"number":3102,"owner":3020,"repository":3021,"state":3039,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### 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_",[3101],{"name":3079,"color":3080},236,"Long Authorization example doesnt display nicely","2025-06-22T12:55:43Z","https://github.com/enzonotario/vitepress-openapi/issues/236",0.82267076,{"description":3108,"labels":3109,"number":3050,"owner":3020,"repository":3021,"state":3039,"title":3111,"updated_at":3112,"url":3113,"score":3114},"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",[3110],{"name":3060,"color":3061},"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.8232894,["Reactive",3116],{},["Set"],["ShallowReactive",3119],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0oT-KXWIbVbJD_n2actLqMMa4eTRlfc8wlZgSaA9Zro":-1},"/enzonotario/vitepress-openapi-starter/1"]