",[],288,"enzonotario","vitepress-openapi","open","Support rendering model-with-annotated-enumeration in Request Body schema","2025-07-30T10:58:09Z","https://github.com/enzonotario/vitepress-openapi/issues/288",0.85238487,{"description":3028,"labels":3029,"number":3036,"owner":3020,"repository":3021,"state":3037,"title":3038,"updated_at":3039,"url":3040,"score":3041},"### What would you like?\n\nRight now It generate such page \r\n\r\n\r\nwould like to remove Default on the side and move the table of content to the left\r\n\r\nOr alternatively, if I could change the name and add a description so the left do not feel emptu\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_",[3030,3033],{"name":3031,"color":3032},"enhancement","a2eeef",{"name":3034,"color":3035},"question","d876e3",109,"closed","Any way to remove default or change the name and add description","2024-11-03T03:36:50Z","https://github.com/enzonotario/vitepress-openapi/issues/109",0.8086284,{"description":3043,"labels":3044,"number":3045,"owner":3020,"repository":3021,"state":3037,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### What would you like?\r\n\r\nFirst of all, thank you for providing this great library!\r\n\r\nIt would be great to show operation parameter descriptions, e.g. \r\n\r\n> _**GetBooks**_\r\n> \r\n> _Parameters_\r\n> **pageIndex**: The number of the page to request. The page starts with the value 0\r\n> **sort**: The field to sort the results by. Prefix by \"-\" to invert the sort.\r\n\r\n### Why is this needed?\r\n\r\nJust the name might not be sufficient for users to understand how to use a certain field. OpenAPI provides the description field for further context.\r\n\r\n### How could it be implemented?\r\n\r\nSince the parameter name, required status, and example are already shown in the \"try-it\" section, it would make sense to show the description there as well.\r\n\r\nAlternatively, parameters could be listed in a section above the response documentation.\r\n\r\n### Other information\r\n\r\nI'd be happy to help with the implementation!",[],102,"Show description field of operation parameters","2024-10-30T19:52:59Z","https://github.com/enzonotario/vitepress-openapi/issues/102",0.81395704,{"description":3051,"labels":3052,"number":3053,"owner":3020,"repository":3021,"state":3037,"title":3054,"updated_at":3055,"url":3056,"score":3057},"Tried on 0.0.3-alpha.63, and 0.0.3-alpha.79 (latest release)\n\nI have a header such as this defined\n\n```\n {\n \"description\": \"Optionally provide parameters as a JSON object in this header. If both query params and X-Query overlap, a 400 error is returned.\",\n \"example\": \"{\\\"id\\\":\\\"1\\\"}\",\n \"in\": \"header\",\n \"name\": \"X-Query\",\n \"schema\": {\n \"type\": \"string\"\n }\n }\n```\n\nBut also a param like this\n\n```\n {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"in\": \"query\",\n \"name\": \"id\",\n \"schema\": {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"example\": \"1\",\n \"form\": \"id\",\n \"type\": \"string\"\n }\n },\n```\n\nBoth of these examples are used by the UI component, and provided in the default try it requests.\nHowever this means that the request will always fail, as the examples conflict with each other.\nHowever, I want to be able to provide real examples to both of these...\n\nI think that either\n1) Examples should not be used in the default try it param\n2) There should be an option to disable it?",[],221,"example should not always be used as the default for the UI","2025-05-18T01:43:41Z","https://github.com/enzonotario/vitepress-openapi/issues/221",0.81714004,{"description":3059,"labels":3060,"number":19,"owner":3020,"repository":3021,"state":3037,"title":3062,"updated_at":3063,"url":3064,"score":3065},"I believe the currentl link prefix is hardcoded `link: `/operations/${c}``\r\n\r\nHowever ultimately I would like to link to 2 different specs under 2 different URL prefixes, such as...\r\n - `http://localhost:5173/apis/v2/`\r\n - `http://localhost:5173/apis/v1/`\r\n\r\nTo do this I guess I would need to pass a prefix into the methods such as `generateSidebarGroup`\r\n\r\nMy current code is:\r\n\r\n```\r\n {\r\n text: 'Version 2',\r\n link: '/apis/v2',\r\n items: [\r\n sidebar.generateSidebarGroup([\"users\", \"published\"],\"Users\"),\r\n ],\r\n },\r\n```",[3061],{"name":3031,"color":3032},"Custom sidebar menu item link","2024-09-18T01:38:40Z","https://github.com/enzonotario/vitepress-openapi/issues/38",0.83189267,{"description":3067,"labels":3068,"number":3070,"owner":3020,"repository":3021,"state":3037,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### What would you like?\n\nHow can I create my own custom components to implement my own needs?\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_",[3069],{"name":3034,"color":3035},229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.8346243,{"description":3076,"labels":3077,"number":3078,"owner":3020,"repository":3079,"state":3037,"title":3080,"updated_at":3081,"url":3082,"score":3083},"Hola buenas tardes estimados, no se esta actualizando el valor del dolar bolsa.",[],44,"esjs-dolar-api","[HOTFIX] Dolar MEP no esta actualizandose","2025-04-16T16:04:37Z","https://github.com/enzonotario/esjs-dolar-api/issues/44",0.8422537,{"description":3085,"labels":3086,"number":3088,"owner":3020,"repository":3021,"state":3037,"title":3089,"updated_at":3090,"url":3091,"score":3092},"### What would you like?\n\nI'd love it if there was an easy to use component that allowed displaying a link that looked like the nice fancy sidebars\n\nThis should be documented\n\n\n\nI'd like to be able to use this anywhere in text\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_",[3087],{"name":3031,"color":3032},222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.8425796,{"description":3094,"labels":3095,"number":3097,"owner":3020,"repository":3021,"state":3037,"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":3031,"color":3032},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.8433853,{"description":3103,"labels":3104,"number":2391,"owner":3020,"repository":3079,"state":3037,"title":3105,"updated_at":3106,"url":3107,"score":3108},"Uso query params para invalidar caché pero en la API al incluir cualquier cosa a la URL hace que devuelva 404. Creo que debería devolver el recurso ignorando los params\r\n\r\nEjemplo: https://dolarapi.com/v1/dolares/blue?t=2023-01-16",[],"URL con querystring devuelve 404","2024-01-20T00:15:10Z","https://github.com/enzonotario/esjs-dolar-api/issues/12",0.8441674,["Reactive",3110],{},["Set"],["ShallowReactive",3113],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7KDd8wMUQ_f3fz4fE-xyKbqVTKQawgKnGzECjd72GGw":-1},"/enzonotario/esjs-dolar-api/29"]