\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":3197,"labels":3198,"number":3199,"owner":3172,"repository":3173,"state":3191,"title":3200,"updated_at":3201,"url":3202,"score":3203},"1、In the file upload scenario, when the browser initiates a request, the header Content-Type does not contain a boundary parameter; normally, when making a request in Postman with a content-type of multipart/form-data, the boundary parameter is automatically included\nthe openai.json:\n\u003Cimg width=\"568\" height=\"832\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e6ec6b35-60cb-4632-bc8b-63fc1cd7ae19\" />\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,"upload and download issues","2025-08-12T23:37:59Z","https://github.com/enzonotario/vitepress-openapi/issues/279",0.7420552,{"description":3205,"labels":3206,"number":3210,"owner":3172,"repository":3173,"state":3191,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### 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_",[3207],{"name":3208,"color":3209},"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":3216,"labels":3217,"number":3221,"owner":3172,"repository":3173,"state":3191,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### 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_",[3218],{"name":3219,"color":3220},"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":3227,"labels":3228,"number":3229,"owner":3172,"repository":3173,"state":3191,"title":3230,"updated_at":3231,"url":3232,"score":3233},"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":3235,"labels":3236,"number":3238,"owner":3172,"repository":3173,"state":3191,"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":3219,"color":3220},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.79620457,{"description":3244,"labels":3245,"number":3247,"owner":3172,"repository":3173,"state":3191,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### 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_",[3246],{"name":3208,"color":3209},168,"Headers are passed wrong to Samples","2025-02-03T01:59:38Z","https://github.com/enzonotario/vitepress-openapi/issues/168",0.7971944,{"description":3253,"labels":3254,"number":3255,"owner":3172,"repository":3173,"state":3191,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### 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.80756634,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMVTHgBBY5L8q20uEXxjQgAzTh-1E1ltovvNIS48hR1g":-1},"/enzonotario/vitepress-openapi/227"]