\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? :)",[2908],{"name":2880,"color":2881},"Enable rendering components for multiple specs on a single page.","2024-09-28T15:44:23Z","https://github.com/enzonotario/vitepress-openapi/issues/21",0.8458671,{"description":2914,"labels":2915,"number":2918,"owner":2869,"repository":2870,"state":2871,"title":2919,"updated_at":2920,"url":2921,"score":2922},"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?",[2916,2917],{"name":2866,"color":2867},{"name":2880,"color":2881},46,"Too many response codes results in element overlap","2024-09-20T01:51:07Z","https://github.com/enzonotario/vitepress-openapi/issues/46",0.8524158,{"description":2924,"labels":2925,"number":2929,"owner":2869,"repository":2870,"state":2871,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### What would you like?\n\nCurrently, When typing in the search box, no api get shown even if they should match the query\r\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_",[2926],{"name":2927,"color":2928},"question","d876e3",115,"api should appear in search","2024-11-04T00:50:21Z","https://github.com/enzonotario/vitepress-openapi/issues/115",0.8556743,{"description":2935,"labels":2936,"number":104,"owner":2869,"repository":2938,"state":2871,"title":2939,"updated_at":2940,"url":2941,"score":2942},"El api esta devolviendo tna null cuando en la pagina es 73,5\r\n\r\n {\r\n \"entidad\": \"BANCO COMAFI SOCIEDAD ANONIMA\",\r\n \"logo\": \"https://www.bcra.gob.ar/Imagenes/logosbancos1/00299.jpg\",\r\n \"tnaClientes\": null,\r\n \"tnaNoClientes\": null,\r\n \"enlace\": \"https://plazofijodigital.comafi.com.ar/#/simulator/form\"\r\n },",[2937],{"name":2866,"color":2867},"esjs-argentina-datos-api","Error en tasa banco comafi","2024-03-12T15:50:38Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/3",0.8580365,{"description":2944,"labels":2945,"number":2947,"owner":2869,"repository":2870,"state":2871,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### 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_",[2946],{"name":2880,"color":2881},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.85851526,{"description":2953,"labels":2954,"number":2955,"owner":2869,"repository":2956,"state":2871,"title":2957,"updated_at":2958,"url":2959,"score":2960},"Buenas! Qué tal?\r\n\r\nEstoy viendo un error en la cotización del Peso Chileno, probablemente relacionado con otro issue cerrado que leí recién, donde el valor hay que dividirlo por 100 para que esté bien. Esto es lo que está mostrando ahora:\r\n\r\n\r\n\r\nMil gracias por API!!\r\nSaludos!\r\n\r\n",[],29,"esjs-dolar-api","Error en la cotización del Peso Chileno","2024-09-06T21:40:13Z","https://github.com/enzonotario/esjs-dolar-api/issues/29",0.8723686,["Reactive",2962],{},["Set"],["ShallowReactive",2965],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fXxxejxSu1HTF_ZFFrVvhMx8H8cLLmbk-V0BsYoSavJc":-1},"/enzonotario/esjs-dolar-api/34"]