\n\n### Desired behavior\n\nA performance score of 90 or above\n\n### Reproduction\n\nhttps://vitepress-openapi.vercel.app/example/operations/getAllArtists.html\n\n### Steps to reproduce\n\n- Open any page generated by this plugin\n- Open Lighthouse\n- Look at the performance score\n",[2867,2870],{"name":2868,"color":2869},"enhancement","a2eeef",{"name":2871,"color":2872},"help wanted","008672",171,"enzonotario","vitepress-openapi","open","Performance issues","2025-02-08T02:57:38Z","https://github.com/enzonotario/vitepress-openapi/issues/171",0.81341285,{"description":2882,"labels":2883,"number":2885,"owner":2874,"repository":2875,"state":2886,"title":2887,"updated_at":2888,"url":2889,"score":2890},"### What would you like?\n\nI'd like to be able to render the openapi specification with a signle column layout. It would be nice if it is configurable in the parameters of the components like OASpec or globally in the theme config. In addition to that, it would also be nice if the different child components could be enabled/disabled (i.e. turn off samples). \n\n### Why is this needed?\n\nI want this because the standard theme does not have a lot of content width, Having a two column layout looks crowded and sometimes the content is wrapped. Having all the child components below each other with a single column layout would bring more clarity to the rendered documentation.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[2884],{"name":2868,"color":2869},91,"closed","Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.7204595,{"description":2892,"labels":2893,"number":2001,"owner":2874,"repository":2897,"state":2886,"title":2898,"updated_at":2899,"url":2900,"score":2901},"# Agregar Aplicación a la lista de aplicaciones que consumen DolarApi.com\n\n## Información de la Aplicación\n\n- **Nombre de la Aplicación:**\n Dólar Ahora\n\n- **URL de la Aplicación:**\n https://play.google.com/store/apps/details?id=com.fraancogaalfras.dolarahora\n\n- **Descripción de la Aplicación:**\n App móvil para consultar el precio de los dólares financieros en Argentina.\n",[2894],{"name":2895,"color":2896},"documentation","0075ca","esjs-dolar-api","Listar Aplicación - Dólar Ahora","2025-03-01T20:46:40Z","https://github.com/enzonotario/esjs-dolar-api/issues/39",0.74422055,{"description":2903,"labels":2904,"number":352,"owner":2874,"repository":2875,"state":2886,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Current behavior\n\nWhen showing operations by path, the full path name is not shown for sub-paths of the operation. This can slightly be worked around by flattening to a depth of 2, but this does not work if there are no other paths after.\n\nFor example, if you have the paths /artists and /artists/{id} it will just show /artists and then /{id} as the sub-path below it.\n\nYou can see this in the stackblitz example here: [stackblitz example](https://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-cqsbxmar?file=public%2Fopenapi.json) (forked from an example you provided another user)\n\nIf you look, you'll notice that the globalv2/attachments/{id} has the issue even when flattening. You can see the same behavior for /artists in the example if you remove the /user/signup endpoint from openapi.json. For some reason, the existence of another endpoint after the /{id} does allow it to show the full path for those /{id} endpoints.\n\n\n\n\n\n### Desired behavior\n\nThe desired behavior would be to have the full path shown for sub-paths and not just show /{id}, even when there are no other sub-paths to the group of items.\n\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-cqsbxmar?file=public%2Fopenapi.json\n\n### Steps to reproduce\n\nOpen the sidebar and view the paths documented. Without flattening, the sub-path will always just show /{id}. If you flatten to a depth of 2, it will resolve the issue unless there are no other endpoints after the /{id} sub-path.\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[],"Issue showing full path name when showing operations by path","2025-01-29T14:29:13Z","https://github.com/enzonotario/vitepress-openapi/issues/163",0.7606794,{"description":2910,"labels":2911,"number":2916,"owner":2874,"repository":2875,"state":2886,"title":2917,"updated_at":2918,"url":2919,"score":2920},"On my site I have the following in my vitepress config\r\n\r\n```\r\n search: {\r\n provider: 'local'\r\n }\r\n```\r\n\r\nper https://vitepress.dev/reference/default-theme-search\r\n\r\nHowever, pages rendered via the method suggested `*.paths.js` doesnt appear in the search.\r\n\r\n\r\n\r\nSeemingly none of the example sites currently include search, and thus the component doesnt appear to work with search?",[2912,2913],{"name":2895,"color":2896},{"name":2914,"color":2915},"question","d876e3",47,"Working example with search provider local set","2024-09-18T12:40:44Z","https://github.com/enzonotario/vitepress-openapi/issues/47",0.78125685,{"description":2922,"labels":2923,"number":2925,"owner":2874,"repository":2897,"state":2886,"title":2926,"updated_at":2927,"url":2928,"score":2929},"",[2924],{"name":2895,"color":2896},37,"Add Dollar Blue for Bolivia","2025-02-17T22:04:29Z","https://github.com/enzonotario/esjs-dolar-api/issues/37",0.7860866,{"description":2931,"labels":2932,"number":2934,"owner":2874,"repository":2875,"state":2886,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### What would you like?\n\nWhen operations with different tags are rendered on the same page, they should be grouped by tags, as it happens in Swagger.\r\n\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_",[2933],{"name":2868,"color":2869},81,"Group operations into tags groups","2024-10-12T13:41:02Z","https://github.com/enzonotario/vitepress-openapi/issues/81",0.7925769,{"description":2940,"labels":2941,"number":2943,"owner":2874,"repository":2897,"state":2886,"title":2944,"updated_at":2945,"url":2946,"score":2947},"- **Descripción de la Aplicación:**\n \u003C!-- Proporciona una breve descripción -->",[2942],{"name":2895,"color":2896},41,"volokokoti","2025-03-04T12:28:13Z","https://github.com/enzonotario/esjs-dolar-api/issues/41",0.80059016,{"description":2949,"labels":2950,"number":2952,"owner":2874,"repository":2875,"state":2886,"title":2953,"updated_at":2954,"url":2955,"score":2956},"Seria interesante que haya una documentación que logre adaptarse al lenguaje seleccionado desde un selector. Ya dependería de uno agregar algún lenguaje adicional en nuestra docs del proyecto. ",[2951],{"name":2868,"color":2869},128,"Multilenguaje ","2024-12-15T03:19:43Z","https://github.com/enzonotario/vitepress-openapi/issues/128",0.81261706,{"description":2958,"labels":2959,"number":2961,"owner":2874,"repository":2875,"state":2886,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### What would you like?\n\nTo be able to define a schema such as the following as a content response\r\n\r\n```\r\n \"schema\": {\r\n \"type\": \"array\",\r\n \"items\": {\r\n \"$ref\": \"#/components/schemas/datapoint\"\r\n }\r\n }\r\n```\r\n\r\nAnd have it display an example using the datapoint schema, rather than just displaying `[]`\n\n### Why is this needed?\n\nMore useful infomation via examples to users.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\nCurrent example just looks like this\r\n\r\n\r\n",[2960],{"name":2868,"color":2869},131,"Display better response examples for arrays of a schema","2024-12-12T09:25:53Z","https://github.com/enzonotario/vitepress-openapi/issues/131",0.81943387,["Reactive",2967],{},["Set"],["ShallowReactive",2970],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBR37pyXLuKvw4UpBmrPC21Rh32_NMzFyAx2mP84i7t0":-1},"/enzonotario/vitepress-openapi/129"]