\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.7895789,{"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.8125845,{"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\nProvide and display multiple query param examples for endpoints\n\n### Why is this needed?\n\nOAPIspec allows it, but only the first is displayed by this component\n\n### How could it be implemented?\n\nRather than display one line with one value\r\n\r\nMultiple lines could be displayed.\n\n### Other information\n\n_No response_",[3044],{"name":3020,"color":3021},130,"closed","Allow multiple query param examples","2024-12-12T14:37:35Z","https://github.com/enzonotario/vitepress-openapi/issues/130",0.80695075,{"description":3052,"labels":3053,"number":3057,"owner":3026,"repository":3058,"state":3046,"title":3059,"updated_at":3060,"url":3061,"score":3062},"Hola buenos dias estimados queria consultarles el horario de actualizacion que tienen para el Dolar Bolsa para no realizar requests de más. Desde ya muchas gracias",[3054],{"name":3055,"color":3056},"question","d876e3",42,"esjs-dolar-api","Consulta horarios de actualizacion","2025-03-20T18:46:11Z","https://github.com/enzonotario/esjs-dolar-api/issues/42",0.8086745,{"description":3064,"labels":3065,"number":1661,"owner":3026,"repository":3058,"state":3046,"title":3067,"updated_at":3068,"url":3069,"score":3070},"Es decir, poder pedir mediante un parametro, el dia en el que se quiere preguntar la cotización\r\n\r\nEJEMPLO:\r\n`GET https://dolarapi.com/v1/dolares/bolsa?dia=11/1/2024`\r\n`GET https://dolarapi.com/v1/dolares/bolsa?dia=01/1/2024`\r\netc\r\no similar.",[3066],{"name":3020,"color":3021},"[New feature] Cotizacion historica","2024-01-21T20:55:50Z","https://github.com/enzonotario/esjs-dolar-api/issues/11",0.81386334,{"description":3072,"labels":3073,"number":1661,"owner":3026,"repository":3027,"state":3046,"title":3074,"updated_at":3075,"url":3076,"score":3070},"Currently parameters are rendered in the docs side (left side) however such parameters are not provided to easily copy and paste in the sample code\r\n\r\n\r\n\r\nThis relates closely to https://github.com/enzonotario/vitepress-theme-openapi/issues/10 (for the sample code part)",[],"BUG: Parameters dont show in sample code, if only in:query","2024-08-27T22:50:49Z","https://github.com/enzonotario/vitepress-openapi/issues/11",{"description":3078,"labels":3079,"number":3057,"owner":3026,"repository":3027,"state":3046,"title":3081,"updated_at":3082,"url":3083,"score":3084},"Follow on to https://github.com/enzonotario/vitepress-theme-openapi/issues/10\r\n\r\nIt would be great to allow trying out requests that have a body required.\r\n\r\nProbably a first version of this would just provide a single text input box for the whole \"body\" to be provided.\r\n\r\nUsers could then easily copy and paste the example (probably json) body, and modify it",[3080],{"name":3020,"color":3021},"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.81657475,{"description":3086,"labels":3087,"number":1559,"owner":3026,"repository":3058,"state":3046,"title":3089,"updated_at":3090,"url":3091,"score":3092},"¡Hola! **Sugiero que la API añada una nueva cotización del dólar.** Específicamente el **Dólar Tarjeta.** Tengo una aplicación que consumiría de la API para calcular los precios finales de los juegos en Steam. \r\n\r\nLos precios se calculan en base al Dólar Tarjeta, que es una cotización diferente de las demás, y que la API no posee. \r\n**Adjunto un enlace en el que se tiene el valor actualizado día a día del Dólar Tarjeta:** [Cotización del dólar tarjeta vía El Cronista](https://www.cronista.com/MercadosOnline/moneda.html?id=ARSTAR)\r\n\r\nQue tenga un endpoint como...\r\n`/v1/dolares/cronista/tarjeta`\r\n\r\nAgradecería muchísimo esta nueva característica. Ya que esto, posibilitaría que la aplicación mía ([Impue-Steam](https://impue-steam.netlify.app/)) funcione correctamente.\r\n\r\nMuchísimas gracias de antemano.",[3088],{"name":3020,"color":3021},"[New feature] Agregar nueva cotización: Dólar Tarjeta","2023-11-06T21:47:37Z","https://github.com/enzonotario/esjs-dolar-api/issues/5",0.820194,{"description":3094,"labels":3095,"number":3097,"owner":3026,"repository":3027,"state":3046,"title":3098,"updated_at":3099,"url":3100,"score":3101},"The generated example code looks like this...\n\n```\ncurl 'https://api.foo/v2/devices/%7Bid%7D/tags' \\\n --header 'Authorization: xxx'\n```\n\nHowever really in the UI it would be nicer to look like\n\n```\ncurl 'https://api.foo/v2/devices/{id}/tags' \\\n --header 'Authorization: xxx'\n```",[3096],{"name":3020,"color":3021},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.8225686,{"description":3103,"labels":3104,"number":3105,"owner":3026,"repository":3058,"state":3046,"title":3106,"updated_at":3107,"url":3108,"score":3109},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],40,"H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.82417756,["Reactive",3111],{},["Set"],["ShallowReactive",3114],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQUJ_m0pidxzBCKuqCjAFMQmwUL0sgcM_c0Y7v94otfI":-1},"/enzonotario/esjs-dolar-api/38"]