",[],288,"Support rendering model-with-annotated-enumeration in Request Body schema","2025-08-11T22:29:43Z","https://github.com/enzonotario/vitepress-openapi/issues/288",0.77438134,{"description":3200,"labels":3201,"number":3203,"owner":3172,"repository":3173,"state":3186,"title":3204,"updated_at":3205,"url":3206,"score":3207},"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",[3202],{"name":3183,"color":3184},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.79593986,{"description":3209,"labels":3210,"number":3211,"owner":3172,"repository":3173,"state":3186,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### 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.7981674,{"description":3217,"labels":3218,"number":3219,"owner":3172,"repository":3173,"state":3186,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Current behavior\n\nGiven this schema:\n```yaml\nopenapi: 3.1.0\ninfo: \n title: test\n version: '0.1'\npaths:\n /test:\n get:\n parameters:\n - in: query\n name: code\n examples:\n name_1:\n value: parameter_value_1\n name_2:\n value: parameter_value_1\n schema:\n type: string\n examples: \n - schema_value_1\n - schema_value_2\n```\n\nThe ui shows `schema_value_1` prefilled for `code` parameter which is incorrect.\n\n### Desired behavior\n\nFor GUI openapi tools `examples` from parameter object itself should be used.\nSo prefilled value should be `parameter_value_1` and not `schema_value_1`\n\nhttps://editor-next.swagger.io also uses examples from parameter object. OpenAPI specification itself does not mention `examples` under `schema` field since it is json-schema field and not OpenAPI specific field.",[],298,"`examples` field is not populated from parameter object","2025-08-27T11:00:31Z","https://github.com/enzonotario/vitepress-openapi/issues/298",0.8042671,{"description":3180,"labels":3225,"number":736,"owner":3172,"repository":3230,"state":3186,"title":3231,"updated_at":3232,"url":3233,"score":3234},[3226,3227],{"name":3183,"color":3184},{"name":3228,"color":3229},"good first issue","7057ff","senadores","Footer con link a argentina datos y al repo open source","2025-02-22T14:02:09Z","https://github.com/enzonotario/senadores/issues/2",0.80478984,{"description":3236,"labels":3237,"number":3239,"owner":3172,"repository":3173,"state":3186,"title":3240,"updated_at":3241,"url":3242,"score":3243},"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```",[3238],{"name":3183,"color":3184},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.81076753,{"description":3245,"labels":3246,"number":3250,"owner":3172,"repository":3173,"state":3186,"title":3251,"updated_at":3252,"url":3253,"score":3254},"Running `docs:dev` results in correct menu items\r\n\r\n\r\n\r\nHowever when actually built, the menu item text doesnt get added\r\n\r\n\r\n\r\nI experienced this while moving from `^0.0.3-alpha.31` to `0.0.3-alpha.37`",[3247],{"name":3248,"color":3249},"bug","d73a4a",84,"menu item text not rendering at build (after `^0.0.3-alpha.31` to `0.0.3-alpha.37`)","2024-10-11T23:44:49Z","https://github.com/enzonotario/vitepress-openapi/issues/84",0.8151384,{"description":3180,"labels":3256,"number":1612,"owner":3172,"repository":3260,"state":3186,"title":3261,"updated_at":3262,"url":3263,"score":3264},[3257],{"name":3258,"color":3259},"documentation","0075ca","esjs-dolar-api","Add Dollar Blue for Bolivia","2025-02-17T22:04:29Z","https://github.com/enzonotario/esjs-dolar-api/issues/37",0.8184867,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fW_g_45NM22aPx58TQt-7Lcv-B3o0C2-f_LINfjccCx4":-1},"/enzonotario/vitepress-openapi/111"]