\n",[],"vitepress-openapi-starter","File upload and download issues","2025-07-24T07:43:57Z","https://github.com/enzonotario/vitepress-openapi-starter/issues/1",0.82506806,{"description":3035,"labels":3036,"number":3040,"owner":3019,"repository":3020,"state":3041,"title":3042,"updated_at":3043,"url":3044,"score":3045},"",[3037],{"name":3038,"color":3039},"enhancement","a2eeef",125,"closed","Add support for `prefixItems` in Schema UI","2025-05-03T22:13:14Z","https://github.com/enzonotario/vitepress-openapi/issues/125",0.7351259,{"description":3047,"labels":3048,"number":3050,"owner":3019,"repository":3020,"state":3041,"title":3051,"updated_at":3052,"url":3053,"score":3054},"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",[3049],{"name":3038,"color":3039},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.79593986,{"description":3056,"labels":3057,"number":3058,"owner":3019,"repository":3020,"state":3041,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### 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":3035,"labels":3064,"number":734,"owner":3019,"repository":3069,"state":3041,"title":3070,"updated_at":3071,"url":3072,"score":3073},[3065,3066],{"name":3038,"color":3039},{"name":3067,"color":3068},"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":3075,"labels":3076,"number":3078,"owner":3019,"repository":3020,"state":3041,"title":3079,"updated_at":3080,"url":3081,"score":3082},"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```",[3077],{"name":3038,"color":3039},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.81076753,{"description":3084,"labels":3085,"number":3089,"owner":3019,"repository":3020,"state":3041,"title":3090,"updated_at":3091,"url":3092,"score":3093},"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`",[3086],{"name":3087,"color":3088},"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":3035,"labels":3095,"number":1596,"owner":3019,"repository":3099,"state":3041,"title":3100,"updated_at":3101,"url":3102,"score":3103},[3096],{"name":3097,"color":3098},"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,{"description":3105,"labels":3106,"number":1225,"owner":3019,"repository":3107,"state":3041,"title":3108,"updated_at":3109,"url":3110,"score":3111},"Hi @enzonotario \r\n\r\nFirst of all, thank you for this repo! It is very helpful.\r\nI followed exactly the steps you wrote, but i get a strange error, and i ran out of ideas what could be wrong. I receive an error message from Pusher in the console saying: json returned from auth endpoint was invalid, yet status code was 200.\r\nIn the DevTools i see that it hits the authEndpoint with status code 200, but as a response i get back the content of my app.blade.php. It is really strange. Do you have any idea what could cause this?\r\n\r\nIt's not just my app. I downloaded and installed this repo of yours, and i get the same error.",[],"lighthouse-laravel-websockets","json returned from auth endpoint was invalid, yet status code was 200.","2020-04-16T18:51:33Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/6",0.82098424,["Reactive",3113],{},["Set"],["ShallowReactive",3116],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fW_g_45NM22aPx58TQt-7Lcv-B3o0C2-f_LINfjccCx4":-1},"/enzonotario/vitepress-openapi/111"]