\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-07-24T13:26:47Z","https://github.com/enzonotario/vitepress-openapi/issues/279",0.8350504,{"description":3035,"labels":3036,"number":3040,"owner":3019,"repository":3020,"state":3041,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Current behavior\n\n\n\n### Desired behavior\n\nI'm not sure what the desired behaviour should be here.\nHowever the `xxx` is seemingly hardcoded in the components currently, and i half would have expected the example to override this based on the behaviours of other parameter and variables examples in the playground.\n\nIt might even be nicer to just have the default auth actually always be an empty string rather than xxx?\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nJust provide an example, and see it not appear in the playground...\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3037],{"name":3038,"color":3039},"enhancement","a2eeef",237,"closed","Authorization example not shown in playground, inconsistent with other examples?","2025-06-22T12:55:44Z","https://github.com/enzonotario/vitepress-openapi/issues/237",0.69705397,{"description":3047,"labels":3048,"number":3050,"owner":3019,"repository":3020,"state":3041,"title":3051,"updated_at":3052,"url":3053,"score":3054},"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```",[3049],{"name":3038,"color":3039},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.7187596,{"description":3056,"labels":3057,"number":3058,"owner":3019,"repository":3020,"state":3041,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### 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,"Is the application/x-www-form-urlencoded content type supported?","2025-05-29T23:41:20Z","https://github.com/enzonotario/vitepress-openapi/issues/227",0.75418013,{"description":3064,"labels":3065,"number":3069,"owner":3019,"repository":3020,"state":3041,"title":3070,"updated_at":3071,"url":3072,"score":3073},"My rendered component looks something like this\r\n\r\n\r\n\r\nHowever the define route doesnt require authentication\r\n\r\n```\r\n \"/users/login\": {\r\n \"post\": {\r\n \"description\": \"lalala.\",\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/LoginRequest\"\r\n }\r\n }\r\n },\r\n \"description\": \"Login\",\r\n \"required\": true\r\n },\r\n \"responses\": {\r\n \"200\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/LoginResponse\"\r\n }\r\n }\r\n },\r\n \"description\": \"OK\"\r\n },\r\n },\r\n \"summary\": \"Login\",\r\n \"tags\": [\r\n \"users\"\r\n ]\r\n }\r\n },\r\n```\r\n\r\nOther endpoints do specify it as a requirement\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ],\r\n```\r\n\r\nAnd it is defined as a schema in the spec\r\n\r\n```\r\n \"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"in\": \"header\",\r\n \"name\": \"Authorization\",\r\n \"type\": \"apiKey\"\r\n }\r\n }\r\n```\r\n\r\nBut it should not be rendered by default unless they are deinfed in a top level `security` section\r\n\r\nSee https://swagger.io/docs/specification/authentication/ `Step 2.`",[3066],{"name":3067,"color":3068},"bug","d73a4a",36,"securitySchemes should only be applied to routes that require it","2024-09-14T16:10:12Z","https://github.com/enzonotario/vitepress-openapi/issues/36",0.78476465,{"description":3075,"labels":3076,"number":3078,"owner":3019,"repository":3020,"state":3041,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### 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_",[3077],{"name":3038,"color":3039},222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.7992082,{"description":3084,"labels":3085,"number":3087,"owner":3019,"repository":3020,"state":3041,"title":3088,"updated_at":3089,"url":3090,"score":3091},"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",[3086],{"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.8063007,{"description":3093,"labels":3094,"number":3095,"owner":3019,"repository":3020,"state":3041,"title":3096,"updated_at":3097,"url":3098,"score":3099},"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,"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.807354,{"description":3101,"labels":3102,"number":3103,"owner":3019,"repository":3020,"state":3041,"title":3104,"updated_at":3105,"url":3106,"score":3107},"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.80786836,["Reactive",3109],{},["Set"],["ShallowReactive",3112],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKRzPx5KxVOq5diQn89L_63ArC2Vyh5fjy2UyDNRxbks":-1},"/enzonotario/vitepress-openapi/236"]