\r\n\r\n\r\n\r\n### Why is this needed?\r\n\r\nThis is useful for endpoints that accept different request bodies\r\n\r\n### How could it be implemented?\r\n\r\nImplement and show a select element when examples are present in openapi.json:\r\n\r\n```\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/ExamplePost\"\r\n },\r\n \"examples\": {\r\n \"Example 1\": {\r\n \"summary\": \"Creating example 1\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\"\r\n }\r\n },\r\n \"example 2\": {\r\n \"summary\": \"Creating example 2\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\",\r\n \"phone_number\": \"123456789\"\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"required\": true\r\n },\r\n```\r\n\r\n### Other information\r\n\r\nI couldn't find this anywhere in the documentation, but if it is already possible i would like to know how. Thank you!",[2891],{"name":2892,"color":2893},"enhancement","a2eeef",141,"vitepress-openapi","Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.81772673,{"description":2901,"labels":2902,"number":1665,"owner":2870,"repository":2871,"state":2872,"title":2903,"updated_at":2904,"url":2905,"score":2906},"https://www.bcra.gob.ar/Catalogo/apis.asp?fileName=central-deudores-v1§ionName=Central%20de%20Deudores",[],"Sumar datos de las APIs de deudores del BCRA","2025-02-19T00:26:37Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/11",0.82595646,{"description":2908,"labels":2909,"number":2914,"owner":2870,"repository":2895,"state":2872,"title":2915,"updated_at":2916,"url":2917,"score":2918},"Example\r\n\r\n\r\n\r\n200,400,401,429,500\r\n\r\nPerhaps it could / should be a drop down if there are more than 4?",[2910,2913],{"name":2911,"color":2912},"bug","d73a4a",{"name":2892,"color":2893},46,"Too many response codes results in element overlap","2024-09-20T01:51:07Z","https://github.com/enzonotario/vitepress-openapi/issues/46",0.83145094,{"description":2920,"labels":2921,"number":2923,"owner":2870,"repository":2895,"state":2872,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### 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.",[2922],{"name":2892,"color":2893},92,"Modify Sample Code Based on Variables","2024-11-15T02:40:07Z","https://github.com/enzonotario/vitepress-openapi/issues/92",0.8393275,{"description":2929,"labels":2930,"number":2931,"owner":2870,"repository":2883,"state":2872,"title":2932,"updated_at":2933,"url":2934,"score":2935},"# Agregar Aplicación a la lista de aplicaciones que consumen DolarApi.com\r\n\r\n## Información de la Aplicación\r\n\r\n- **Nombre de la Aplicación:**\r\nDolar Info\r\n\r\n- **URL de la Aplicación:**\r\nwww.dolar-info.com\r\n\r\n- **Descripción de la Aplicación:**\r\nAplicación web enfocada en ofrecer información actualizada para analizar indicadores económicos claves de Argentina\r\n",[],25,"Listar Aplicación","2024-07-04T22:22:59Z","https://github.com/enzonotario/esjs-dolar-api/issues/25",0.845078,{"description":2937,"labels":2938,"number":2940,"owner":2870,"repository":2895,"state":2872,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### What would you like?\n\nThere is another package that allows for adding icons to code groups. This is commonly found on other VitePress sites when displaying commands or programming languages. It appears that the code group relies on there being a data-title attribute for it to display icons.\n\nThe code group icon package is called: vitepress-plugin-group-icons\nhttps://github.com/yuyinws/vitepress-plugin-group-icons\n\nYou can see it in use here on the main VitePress site: https://vitepress.dev/guide/getting-started in the installation section.\n\nI should note that the package seems to look for file extensions when displaying language icons but I used custom icons in my implementation so that it could work with the vitepress-openapi implementation.\n\n\n\n### Why is this needed?\n\nIt may be common for people to utilize code group icons elsewhere in their documentation and it would be helpful for the openapi generated pages to be able to display icons in those code groups as well.\n\n### How could it be implemented?\n\nI believe this could be achieved by changing the OACodeSamples component and adding sample.lang in a data-title attribute added to the label. I don't believe this would impact functionality for people not using code group icons but would allow those that are, compatibility when combining it with custom icons.\n\n*I should note that there appears to be some oddities that deal with the capitalization, or lack thereof for the value in the data-title attribute, but I plan to bring that up to the code group icon package maintainer when I can narrow down the issue.\n\n\n\n### Other information\n\n_No response_",[2939],{"name":2892,"color":2893},198,"Request to add data-title attribute to code block group labels","2025-04-13T18:53:02Z","https://github.com/enzonotario/vitepress-openapi/issues/198",0.85092026,{"description":2946,"labels":2947,"number":1577,"owner":2870,"repository":2948,"state":2872,"title":2949,"updated_at":2950,"url":2951,"score":2952},"En dispositivos móviles en la página **/senadores** se desborda el elemento de paginación.\n\nDejo una foto:\n",[],"senadores","Desbordamiento de elementos en la página de senadores","2025-02-24T13:53:35Z","https://github.com/enzonotario/senadores/issues/13",0.85790646,{"description":2954,"labels":2955,"number":2956,"owner":2870,"repository":2895,"state":2872,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Current behavior\n\nFirst of all, thank you for this fantastic theme/addon!\n\nWe are using multiple root levels in our vitepress API (`/api/` and `/sdk/`, etc.) like this. Openapi link generation works, however this way openapi links are not auto activated anymore when clicked or scrolled. \n\n### Desired behavior\n\nSidebar links are marked as active on click or hover.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-2k5lx5mk\n\n### Steps to reproduce\n\n```js\n themeConfig: {\n sidebar: {\n '/api/': {\n base: '/api/',\n items: [\n {\n text: 'API Documentation',\n items: [\n {text: 'Quickstart', link: 'quickstart'},\n ]\n },\n {\n text: 'By Tags',\n items: [\n ...sidebar.itemsByTags(),\n ],\n },\n {\n text: 'By Operations',\n items: [\n ...sidebar.generateSidebarGroups(),\n ],\n }\n ]\n },\n '/sdk/': {\n base: '/sdk/',\n items: [\n {\n text: 'SDK Documentation',\n items: [\n {text: 'Getting Started', link: 'getting-started'},\n ]\n }\n ]\n }\n }\n }\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[],213,"Sidebar items not activating when using base in parent in sidebar","2025-05-01T22:37:29Z","https://github.com/enzonotario/vitepress-openapi/issues/213",0.8579455,["Reactive",2962],{},["Set"],["ShallowReactive",2965],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0tGf9ulP5kzQ2ohFg474cuFL282REpgjW4ux7R7o2iM":-1},"/enzonotario/esjs-dolar-api/14"]