\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",[3019,3022],{"name":3020,"color":3021},"enhancement","a2eeef",{"name":3023,"color":3024},"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":3034,"labels":3035,"number":3036,"owner":3026,"repository":3027,"state":3028,"title":3037,"updated_at":3038,"url":3039,"score":3040},"So, following on from https://github.com/enzonotario/vitepress-openapi/issues/237#issuecomment-2994204686\n\nThis \"issue\" is rather a place to collect my thoughts and discuss, potentially some of these ideas are bad, but its the combination of thoughts given the `xxx` confusion I had, + pulling in thoughts from other tooling I have used.\n\n---\n\n\n\nThe display of `xxx` is unclear to me in terms of what it is trying to communicate.\nIt could be one of these things\n - xxx is the example, a placeholder for you to enter something into\n - It could be representing the fact that a value is there, but we dont want to show you (like `***` for passwords)\n - It could be the actual value saved in local storage? waiting for you to update it?\n\nWhen loading first time and making a request, I actually saw that it made a request with a literal `xxx`\n\n\n\nNot sure if this is something I had entered though?\n\nIt was indeed stored in local storage (and the UI didn't really help me figure that out...)\n\n\n\nDeleting the key from local storage, and I then correctly see the example appear in the latest version\n\n\n\nAs a result, im not sure if https://github.com/enzonotario/vitepress-openapi/issues/237 even was an issue, or rather just I had no idea where the `xxx` was coming from?\n\nSo, I would propose......\n\n**1)When key is stored and coming form local storage, keep it editable**\n\nCurrently when its coming form local storage, it is the placeholder for the field..\n\n\n\nThis makes it appear exactly like the example, and examples else where and thus is easily confused.\n\nI see other API sandboxes just keep / load the field into the text box and leave it there, so perhaps just do that?\n\n**2)Hover text for field saying it is stored between sessions in local storage?**\n\nAgain, a subtle way to make it easier for folks to understand what it going on?\n\n**3)Provide a way to clear from local storage**\n\nPerhaps a small clear button next to the APIKey name?\n\n\n\nMaybe there should even be a save button here rather than doing it automatically?\n\nPerhaps all of what I have said and am saying should be other in the other component?\n\n\n\n**4) Provide an optional button next to token field, to take a user to a page to setup the api key?**\n\nThis could be a custom dedicated page with custom content.\nIt thus could be as simple as just a page with instructions, and also a text box and save button that would put the key in local storage?\nIt could also just be a popup?\n\nPerhaps a default component for use on such as page could be used that takes the key and puts it in the right place in local storage?\n\nAnd perhaps another way of default option that could be provided would be a link to the route page that would generate the token, such as in my case http://localhost:8093/apis/v2/post-users-login\nOnce making the request and getting a response, next to the response would be a button to say \"set as API key\" or such?\nSo this would require some additional options on the route component?\n\nPerhaps something in one of these 3 green places?\n\n",[],246,"Ideas around Authorization saving and population","2025-06-23T08:01:09Z","https://github.com/enzonotario/vitepress-openapi/issues/246",0.8205086,{"description":3042,"labels":3043,"number":3045,"owner":3026,"repository":3027,"state":3046,"title":3047,"updated_at":3048,"url":3049,"score":3050},"### 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_",[3044],{"name":3020,"color":3021},91,"closed","Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.7204595,{"description":3052,"labels":3053,"number":3057,"owner":3026,"repository":3058,"state":3046,"title":3059,"updated_at":3060,"url":3061,"score":3062},"# 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",[3054],{"name":3055,"color":3056},"documentation","0075ca",39,"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":3064,"labels":3065,"number":352,"owner":3026,"repository":3027,"state":3046,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### 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":3071,"labels":3072,"number":3077,"owner":3026,"repository":3027,"state":3046,"title":3078,"updated_at":3079,"url":3080,"score":3081},"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?",[3073,3074],{"name":3055,"color":3056},{"name":3075,"color":3076},"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":3083,"labels":3084,"number":1597,"owner":3026,"repository":3058,"state":3046,"title":3086,"updated_at":3087,"url":3088,"score":3089},"",[3085],{"name":3055,"color":3056},"Add Dollar Blue for Bolivia","2025-02-17T22:04:29Z","https://github.com/enzonotario/esjs-dolar-api/issues/37",0.7860866,{"description":3091,"labels":3092,"number":3094,"owner":3026,"repository":3027,"state":3046,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### 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_",[3093],{"name":3020,"color":3021},81,"Group operations into tags groups","2024-10-12T13:41:02Z","https://github.com/enzonotario/vitepress-openapi/issues/81",0.7925769,{"description":3100,"labels":3101,"number":3103,"owner":3026,"repository":3058,"state":3046,"title":3104,"updated_at":3105,"url":3106,"score":3107},"- **Descripción de la Aplicación:**\n \u003C!-- Proporciona una breve descripción -->",[3102],{"name":3055,"color":3056},41,"volokokoti","2025-03-04T12:28:13Z","https://github.com/enzonotario/esjs-dolar-api/issues/41",0.8005902,{"description":3109,"labels":3110,"number":3112,"owner":3026,"repository":3027,"state":3046,"title":3113,"updated_at":3114,"url":3115,"score":3116},"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. ",[3111],{"name":3020,"color":3021},128,"Multilenguaje ","2024-12-15T03:19:43Z","https://github.com/enzonotario/vitepress-openapi/issues/128",0.812617,["Reactive",3118],{},["Set"],["ShallowReactive",3121],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBR37pyXLuKvw4UpBmrPC21Rh32_NMzFyAx2mP84i7t0":-1},"/enzonotario/vitepress-openapi/129"]