",[],288,"Support rendering model-with-annotated-enumeration in Request Body schema","2025-07-30T10:58:09Z","https://github.com/enzonotario/vitepress-openapi/issues/288",0.859316,{"description":3036,"labels":3037,"number":3041,"owner":3020,"repository":3021,"state":3042,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### 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_",[3038],{"name":3039,"color":3040},"question","d876e3",229,"closed","How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.78302884,{"description":3048,"labels":3049,"number":93,"owner":3020,"repository":3050,"state":3042,"title":3051,"updated_at":3052,"url":3053,"score":3054},"@enzonotario first of all really appreciable as you spare time to help us with this. I am working with nuxtjs ad tried to set it up with nuxtjs using [nuxt-apollo](https://github.com/nuxt-community/apollo-module) module. \r\nI have setup [echo.link.js](https://github.com/enzonotario/lighthouse-laravel-websockets/blob/master/resources/js/echo.link.js) as it is and then in apollo client config (in dedicated file) I have combined the `echoLink` using `ApolloLink.from()` method\r\nI am geting error\r\n`Unexpected token export`\r\nI played around with [echo.link.js](https://github.com/enzonotario/lighthouse-laravel-websockets/blob/master/resources/js/echo.link.js) and changed \r\n`import Echo from 'laravel-echo/dist/echo';`\r\n to \r\nimport Echo from 'laravel-echo';\r\nthen error changes to \r\n`Pusher is not defined` \r\nI have installed pusher via npm too.\r\nCan you please help me with that\r\nagain have no words to say thanks for such a favor ",[],"lighthouse-laravel-websockets","Working with Nuxtjs and vue-apollo nuxt module","2019-09-09T17:21:38Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/1",0.82015055,{"description":3056,"labels":3057,"number":3062,"owner":3020,"repository":3021,"state":3042,"title":3063,"updated_at":3064,"url":3065,"score":3066},"Hey there! First of all, thank you so much for such a cool enhancement to VitePress.\n\nI'm currently using the `By Operation` method of displaying OAS content, i.e. grouping the specific endpoint pages under the tags in the sidebar.\n\nIs it possible to make the categories/groupings collapsed by default, or introduce the collapsing mechanism from VitePress altogether? Something akin to `collapsed: true` [for the VitePress sidebar groups](https://vitepress.dev/reference/default-theme-sidebar#collapsible-sidebar-groups).\n\nHere's a grouping that I would like collapsed, to help visualize this issue:\n\n",[3058,3061],{"name":3059,"color":3060},"documentation","0075ca",{"name":3039,"color":3040},195,"Collapsible operation grouping in the sidebar","2025-04-08T21:55:25Z","https://github.com/enzonotario/vitepress-openapi/issues/195",0.82618815,{"description":3068,"labels":3069,"number":3073,"owner":3020,"repository":3021,"state":3042,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### What would you like?\r\n\r\nList of tags underneath the title\r\n\r\n### Why is this needed?\r\n\r\nWould be handy with tags pages, if one doesn't show tags in the sidebar (without `itemsByTags`)\r\n\r\n### How could it be implemented?\r\n\r\nI use following workaround\r\n\r\n```vue\r\n\u003COAOperation :operationId=\"operationId\" :isDark=\"isDark\" >\r\n \u003Ctemplate #description=\"description\">\r\n \u003Cdiv>\r\n \u003CBadge type=\"info\" v-for=\"tag in operation.tags\">\r\n \u003C!-- hardocde prefix, tell me if you know better way -->\r\n \u003Ca :href=\"`/tags/${tag}`\">{{ tag }}\u003C/a>\r\n \u003C/Badge>\r\n \u003C/div>\r\n \u003C/template>\r\n\u003C/OAOperation>\r\n```\r\n\r\nBut would be nice to have\r\n\r\n```ts\r\nuseTheme({\r\n operation: {\r\n slots: ['tags']\r\n }\r\n})\r\n```\r\n\r\n### Other information\r\n\r\nRelated: it would be nice to have more compact representation of endpoints lists for tags pages. For now I use\r\n\r\n```ts\r\nimport { useTheme } from 'vitepress-openapi'\r\nuseTheme({\r\n operation: {\r\n slots: [\r\n 'header',\r\n 'path',\r\n 'description',\r\n ],\r\n cols: 2,\r\n },\r\n})\r\n```\r\n\r\nWhich looks a bit strange",[3070],{"name":3071,"color":3072},"enhancement","a2eeef",120,"Add tags slot","2024-12-02T03:07:06Z","https://github.com/enzonotario/vitepress-openapi/issues/120",0.8292161,{"description":3079,"labels":3080,"number":3081,"owner":3020,"repository":3021,"state":3042,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### 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.8308208,{"description":3087,"labels":3088,"number":644,"owner":3020,"repository":3090,"state":3042,"title":3091,"updated_at":3092,"url":3093,"score":3094},"Hola!\r\n\r\nLa documentación del endpoint [GET Dólar por casa y fecha](https://argentinadatos.com/docs/operations/get-cotizaciones-dolares-casa-fecha.html) no menciona `contadoconliqui` como un valor válido para `casa`, aunque si lo es. Adjunto fotos de los docs y del endpoint aceptando el valor.\r\n\r\n\u003Cdetails>\u003Csummary>Foto de los docs\u003C/summary>\r\n\r\n\u003Cimg width=\"1091\" alt=\"image\" src=\"https://github.com/user-attachments/assets/62e1efe3-ec78-4a22-a716-570910472dbc\">\r\n\r\n\u003C/details> \r\n\r\n\u003Cdetails>\u003Csummary>Endpoint acepta el valor\u003C/summary>\r\n\r\n\u003Cimg width=\"833\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0634a0ba-a4b4-4e17-a5fd-f3571d24a2b7\">\r\n\r\n\u003C/details> \r\n\r\nMuy buena API, gracias!",[3089],{"name":3059,"color":3060},"esjs-argentina-datos-api","[Docs] Añadir CCL como valor válido para `casa` en GET Dólar por casa y fecha","2024-09-20T01:00:46Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/7",0.83599013,{"description":3096,"labels":3097,"number":3099,"owner":3020,"repository":3021,"state":3042,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### What would you like?\r\n\r\nParameter example values along with the description\r\n\r\nSo for example after I overloaded your template for this section I see this:\r\n\r\n**$filter** string\r\nExample name eq 'hello'\r\n\r\n\r\nYou can see the example [live here](https://apidev.digilean.tools/docs/operations/Boards_List) as well\r\n\r\n### Why is this needed?\r\n\r\nI see you use the example values in the playground/try it section\r\n\r\nBut I choose not to display this.\r\n\r\n### How could it be implemented?\r\n\r\nSomething like \r\n```vue\r\n\u003Cdiv v-if=\"props.parameter.example\" class=\"flex flex-row space-x-2\">\r\n \u003Cspan class=\"text-sm example font-bold\">\r\n Example\r\n \u003C/span>\r\n \u003Cspan class=\"text-sm text-gray-600 dark:text-gray-300\">\r\n {{ props.parameter.example }}\r\n \u003C/span>\r\n\u003C/div>\r\n```\r\n\r\n### Other information\r\n\r\n_No response_",[3098],{"name":3071,"color":3072},93,"Display example values for Parameters","2024-10-17T08:22:46Z","https://github.com/enzonotario/vitepress-openapi/issues/93",0.84709555,{"description":3105,"labels":3106,"number":734,"owner":3020,"repository":3050,"state":3042,"title":3107,"updated_at":3108,"url":3109,"score":3110},"",[],"does it work with v4 lighthouse?","2020-11-07T13:40:11Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/2",0.8490394,["Reactive",3112],{},["Set"],["ShallowReactive",3115],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9wd6TQoVOyz6JhODou8GnDw2uScIWQtHUB8GaMX0UG8":-1},"/enzonotario/vitepress-openapi/154"]