\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? :)",[2875],{"name":2876,"color":2877},"enhancement","a2eeef","vitepress-openapi","Enable rendering components for multiple specs on a single page.","2024-09-28T15:44:23Z","https://github.com/enzonotario/vitepress-openapi/issues/21",0.80261356,{"description":2884,"labels":2885,"number":2889,"owner":2865,"repository":2878,"state":2867,"title":2890,"updated_at":2891,"url":2892,"score":2893},"### Current behavior\n\nOn some route, the schema view is empty even though the json view is not\n\n### Desired behavior\n\nI expect the schema view to always represent the type\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/post-api-scheduling-scheduleExecution.html\r\n# click on Schema view for Request Body, see it is empty\r\n```\r\n\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[2886],{"name":2887,"color":2888},"bug","d73a4a",110,"Schema view empty even though json view is not","2024-11-30T14:09:26Z","https://github.com/enzonotario/vitepress-openapi/issues/110",0.81881434,{"description":2895,"labels":2896,"number":2900,"owner":2865,"repository":2901,"state":2867,"title":2902,"updated_at":2903,"url":2904,"score":2905},"# de tu -->",[2897],{"name":2898,"color":2899},"documentation","0075ca",34,"esjs-dolar-api","Listar Aplicación","2025-02-11T01:31:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/34",0.8233674,{"description":2907,"labels":2908,"number":2910,"owner":2865,"repository":2878,"state":2867,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### 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.",[2909],{"name":2876,"color":2877},92,"Modify Sample Code Based on Variables","2024-11-15T02:40:07Z","https://github.com/enzonotario/vitepress-openapi/issues/92",0.8382431,{"description":2916,"labels":2917,"number":2919,"owner":2865,"repository":2878,"state":2867,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### What would you like?\n\nI wonder if it is possible to implement path based sidebar. For example, we have\r\n\r\n```\r\n/api/v1/products CRUD\r\n/api/v1/orders CRUD\r\n```\r\n\r\nSidebar would look like\r\n\r\n```\r\n/api/v1\r\n ├ products\r\n | ├ PUT\r\n | ├ GET\r\n | ├ POST\r\n | └ DELETE\r\n └ orders\r\n ├ PUT\r\n ├ GET\r\n ├ POST\r\n └ DELETE\r\n```\r\n\r\n**Note**: empty folders are collapsed\r\n\n\n### Why is this needed?\n\nI want to use more than one tag per endpoint. But in this case sidebar looks strange. Maybe there is a way to organize sidebar better even if there are multiple tags...\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[2918],{"name":2876,"color":2877},119,"Path based sidebar","2024-12-12T03:25:21Z","https://github.com/enzonotario/vitepress-openapi/issues/119",0.8449736,{"description":2925,"labels":2926,"number":2928,"owner":2865,"repository":2878,"state":2867,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### What would you like?\r\n\r\nParameter example values along with the description\r\n\r\nSo for example after I overloaded your template for this section I see this:\r\n\r\n**$filter** string\r\nExample name eq 'hello'\r\n\r\n\r\nYou can see the example [live here](https://apidev.digilean.tools/docs/operations/Boards_List) as well\r\n\r\n### Why is this needed?\r\n\r\nI see you use the example values in the playground/try it section\r\n\r\nBut I choose not to display this.\r\n\r\n### How could it be implemented?\r\n\r\nSomething like \r\n```vue\r\n\u003Cdiv v-if=\"props.parameter.example\" class=\"flex flex-row space-x-2\">\r\n \u003Cspan class=\"text-sm example font-bold\">\r\n Example\r\n \u003C/span>\r\n \u003Cspan class=\"text-sm text-gray-600 dark:text-gray-300\">\r\n {{ props.parameter.example }}\r\n \u003C/span>\r\n\u003C/div>\r\n```\r\n\r\n### Other information\r\n\r\n_No response_",[2927],{"name":2876,"color":2877},93,"Display example values for Parameters","2024-10-17T08:22:46Z","https://github.com/enzonotario/vitepress-openapi/issues/93",0.8462321,{"description":2934,"labels":2935,"number":2936,"owner":2865,"repository":2878,"state":2867,"title":2937,"updated_at":2938,"url":2939,"score":2940},"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.8477983,{"description":2942,"labels":2943,"number":659,"owner":2865,"repository":2901,"state":2867,"title":2947,"updated_at":2948,"url":2949,"score":2950},"Hola queria saber si tienen alguna API para consumir el valor de dolar bolsa por fechas pasadas.\r\n\r\nActulamente estoy usando https://dolarapi.com/docs/operations/get-dolar-bolsa.html para obtener el valor del dia, pero quisiera saber si tienen alguna API para consumir valores pasados por fecha.\r\n\r\nSaludos",[2944],{"name":2945,"color":2946},"question","d876e3","Valor dolar bolsa historico","2024-03-01T17:08:36Z","https://github.com/enzonotario/esjs-dolar-api/issues/18",0.8487903,{"description":2952,"labels":2953,"number":659,"owner":2865,"repository":2878,"state":2867,"title":2955,"updated_at":2956,"url":2957,"score":2950},"My spec has a bunch of request property descriptions.\r\n\r\nSomething like this\r\n\r\n```\r\n{\r\n \"properties\": {\r\n \"password\": {\r\n \"description\": \"Password of the user\",\r\n \"type\": \"string\"\r\n },\r\n \"refreshable\": {\r\n \"description\": \"Generate a refresh token, which expires this many seconds after the access token expiry. Max 31 days\",\r\n \"maximum\": 2678400,\r\n \"type\": \"integer\"\r\n }\r\n }\r\n}\r\n```\r\n\r\nCurrently, the request body is just specified as a JSON blob\r\n\r\n\r\n\r\nHow do you think we could / should alter this to include details of descriptions, max, type etc",[2954],{"name":2876,"color":2877},"Request body field (display additional details)","2024-09-28T15:44:43Z","https://github.com/enzonotario/vitepress-openapi/issues/18",["Reactive",2959],{},["Set"],["ShallowReactive",2962],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fB41vzoD-micXh1BrFpUgL5T47MdcgZOUVgH_A1HNXdQ":-1},"/enzonotario/vitepress-openapi/78"]