\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.80339104,{"description":3212,"labels":3213,"number":93,"owner":3174,"repository":3214,"state":3176,"title":3215,"updated_at":3216,"url":3217,"score":3218},"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.8148064,{"description":3220,"labels":3221,"number":3223,"owner":3174,"repository":3175,"state":3176,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### What would you like?\n\nThe ability to change the default url/port for the \"Try It Out\" button. \n\n### Why is this needed?\n\nThe API I'm building has different ports for different things. In my specific case, the current behavior does not invoke my api. \n\n### How could it be implemented?\n\nCould we possibly have an additional env variable that overwrites the default behavior?\n\n### Other information\n\n_No response_",[3222],{"name":3196,"color":3197},127,"Overwrite \"Try It Out\" url","2024-12-21T01:51:19Z","https://github.com/enzonotario/vitepress-openapi/issues/127",0.8223195,{"description":3229,"labels":3230,"number":503,"owner":3174,"repository":3234,"state":3176,"title":3235,"updated_at":3236,"url":3237,"score":3238},"# de tu -->",[3231],{"name":3232,"color":3233},"documentation","0075ca","esjs-dolar-api","Listar Aplicación","2025-02-11T01:31:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/34",0.83008975,{"description":3240,"labels":3241,"number":1028,"owner":3174,"repository":3175,"state":3176,"title":3243,"updated_at":3244,"url":3245,"score":3246},"Currently I have something like this on a single markdown page...\r\n\r\n```\r\n\u003Cscript setup lang=\"ts\">\r\nimport { useRoute, useData } from 'vitepress'\r\nimport { useSidebar, useOpenapi } from 'vitepress-theme-openapi'\r\nimport spec from '../swagger/v2.json' with { type: 'json' }\r\nconst openapi = useOpenapi()\r\nopenapi.setSpec(spec)\r\nconst route = useRoute()\r\nconst { isDark } = useData()\r\n\u003C/script>\r\n\r\n\u003COAOperation operationId=\"post-users-login\" method=\"post\" :isDark=\"isDark\" />\r\n\u003COAOperation operationId=\"post-users-refreshToken\" method=\"post\" :isDark=\"isDark\" />\r\n```\r\n\r\nFurther down the page I would like to include a component rendered from the `../swagger/v1.json` spec, however I believe with the current setup that will not be possible.\r\n\r\nUltimately I think this will require passing the openapi into the components? :)",[3242],{"name":3196,"color":3197},"Enable rendering components for multiple specs on a single page.","2024-09-28T15:44:23Z","https://github.com/enzonotario/vitepress-openapi/issues/21",0.83221257,{"description":3248,"labels":3249,"number":3251,"owner":3174,"repository":3175,"state":3176,"title":3252,"updated_at":3253,"url":3254,"score":3255},"### Current behavior\n\nI am using\r\n\r\n```\r\nuseTheme({\r\n\trequest: {\r\n\t\t// Set the default schema view.\r\n\t\tdefaultView: 'schema', // schema or contentType\r\n\t},\r\n});\r\n```\r\n\r\nto set the default view to schema but this does not work\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:dev\r\n# navigate to http://localhost:5173/api-all-in-one/\r\n# it still use JSON as default view\r\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3250],{"name":3232,"color":3233},107,"useTheme have no effect","2024-11-02T22:51:19Z","https://github.com/enzonotario/vitepress-openapi/issues/107",0.83956254,{"description":3257,"labels":3258,"number":3260,"owner":3174,"repository":3175,"state":3176,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### What would you like?\n\nThe current version generates \"static\" code for each language, based only on the url and method. Unfortunately, the url is simply: `const url = props.baseUrl + props.path`. This has the issue that any path parameters are left as-is in the code.\r\n\r\nIt would be great if the sample code could be updated to include the variables in the \"try it\" box. This way the code sample would be \"complete\". I _think_ this would be done in much the same was as the `OACodeBlock` currently computes the URL for curl\n\n### Why is this needed?\n\nIf you copy-and-paste the code sample as-is, you will end up with an invalid URL if there are path parameters.\r\n\r\nAlso, it would be nice to mix-and-match such that you can _remove_ the try it portion of the playground, but keep the sample code. This way people can \"build\" a request in their language of choice based on the variables form.\n\n### How could it be implemented?\n\nI _think_ you would need to extract (or just duplicate?) the code used to compute the curl information:\r\n\r\n```\r\nconst curl = computed(() => {\r\n const headers = request.value.headers\r\n if (!headers?.['Content-Type']) {\r\n headers['Content-Type'] = 'application/json'\r\n }\r\n\r\n return fetchToCurl({\r\n method: props.method.toUpperCase(),\r\n url: request.value.url,\r\n headers,\r\n body: request.value.body ? formatJson(request.value.body) : null,\r\n })\r\n})\r\n```\r\n\r\nThen pass this as a parameter to `generateCodeSamples` so that it can generate each code sample appropriately.\n\n### Other information\n\nIt would also be _awesome_ to select _which_ languages you want to support, and possibly even some way to provide the template for each language. I realize this is above-and-beyond, but something to think about if you're changing this.",[3259],{"name":3196,"color":3197},92,"Modify Sample Code Based on Variables","2024-11-15T02:40:07Z","https://github.com/enzonotario/vitepress-openapi/issues/92",0.84134316,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fFs9u0kdV4rRe1GeTtF083nxfKYkxgrIkZuvnk0ZQHWE":-1},"/enzonotario/vitepress-openapi/204"]