\n\nthe postman request:\n\u003Cimg width=\"1356\" height=\"550\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d8f101f6-ff4f-4106-bd8f-016970e70c1e\" />\n\n\u003Cimg width=\"1091\" height=\"691\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/92855ba7-fb6c-4526-8db2-5698519cd093\" />\n\n\n\n2、When I call the download file interface, the \"download files\" button is not responding。\n\n\u003Cimg width=\"392\" height=\"274\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/05b06400-49b1-4885-a710-27fc7be3c34e\" />",[],279,"enzonotario","vitepress-openapi","open","upload and download issues","2025-07-24T13:26:47Z","https://github.com/enzonotario/vitepress-openapi/issues/279",0.86446375,{"description":3028,"labels":3029,"number":93,"owner":3020,"repository":3030,"state":3031,"title":3032,"updated_at":3033,"url":3034,"score":3035},"@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","closed","Working with Nuxtjs and vue-apollo nuxt module","2019-09-09T17:21:38Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/1",0.7912328,{"description":3037,"labels":3038,"number":1225,"owner":3020,"repository":3030,"state":3031,"title":3039,"updated_at":3040,"url":3041,"score":3042},"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.",[],"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.8026557,{"description":3044,"labels":3045,"number":1443,"owner":3020,"repository":3030,"state":3031,"title":3046,"updated_at":3047,"url":3048,"score":3049},"Hi There,\r\n\r\nI am here because of this issue: https://github.com/nuwave/lighthouse/issues/1796.\r\n\r\nYour code added to the `ArrayChannelManager` removes _all_ subscriptions connection to the websocket server each time a connection is removed from all channels.\r\n\r\nhttps://github.com/enzonotario/lighthouse-laravel-websockets/blob/222531f198a4722ad9928f39aa7e96474071b6d9/app/WebSockets/Channels/ChannelManager/ArrayChannelManager.php#L16-L19\r\n\r\nThis also removes subscription for other connections, so this code only works if you have a single connection connected, but as you add more connections every time one of them disconnects it will remove _all_ subscriptions.\r\n\r\nMight I suggest you update the example with some of the new ideas from here: https://github.com/nuwave/lighthouse/issues/847#issuecomment-618254044?\r\n\r\nThis way when people use your example they won't have a broken setup like the author of the issue I mentioned earlier.\r\n\r\nThanks for creating it in the first place, a lot of people have a hard time getting it working and we are working towards official support in Lighthouse but until that time I'd appreciate it if you could update!",[],"Warning, this example removes _all_ subscriptions when closing a single connection","2021-04-23T22:45:29Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/17",0.81217027,{"description":3051,"labels":3052,"number":3053,"owner":3020,"repository":3021,"state":3031,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Current behavior\n\nHello,guys\n\nWhen i use that example about the Pages By operation\n\n```md\n---\naside: false\noutline: false\ntitle: vitepress-openapi\n---\n\n\u003Cscript setup lang=\"ts\">\nimport { useRoute } from 'vitepress'\n\nconst route = useRoute()\n\nconst operationId = route.data.params.operationId\n\u003C/script>\n\n\u003COAOperation :operationId=\"operationId\" />\n\n```\n\n```js\nimport { usePaths } from 'vitepress-openapi'\nimport spec from '../../public/test.json' with {type: 'json'}\n\nexport default {\n paths() {\n return usePaths({ spec })\n .getPathsByVerbs()\n .map(({ operationId, summary }) => {\n return {\n params: {\n operationId,\n pageTitle: `${summary} - vitepress-openapi`,\n },\n }\n })\n },\n}\n```\n\nThe terminal show this error,but i dont understand what it mean\n\n\n\nThe terminal guide me the links https://cn.vite.dev/guide/troubleshooting which is show The CJS build of Vite's Node API is deprecated and will be removed in Vite 6. \n\nHope u give the answer thank u so much\n\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n\n\n### Logs and Error Messages\n\n\n\n### Other Information\n\n_No response_",[],212,"Pages by Operation Example dose not work","2025-04-30T22:18:57Z","https://github.com/enzonotario/vitepress-openapi/issues/212",0.8152833,{"description":3059,"labels":3060,"number":2391,"owner":3020,"repository":3030,"state":3031,"title":3061,"updated_at":3062,"url":3063,"score":3064},"Hi,\r\n \r\n Nice work you've done here, but i am wondering if there is a other way to support subscription with lighthouse because is so much work to be done to make it work and there must be a way implemented by them.. or should be 👍 \r\n Also I am wondering if you can tell me.. from what i've checked you trigger a subscription from web/routes.php (home page) by clicking on that button, but you can can make that mutation that you have created work in playground?",[],"Subscription","2020-11-07T13:39:54Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/12",0.82725316,{"description":3066,"labels":3067,"number":2391,"owner":3020,"repository":3021,"state":3031,"title":3074,"updated_at":3075,"url":3076,"score":3064},"My API has a security scheme defined, such as the following\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ],\r\n \"components\": {\r\n \"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"type\": \"apiKey\",\r\n \"in\": \"header\",\r\n \"name\": \"Authorization\"\r\n }\r\n },\r\n```\r\n\r\nWhich can then be interpereted as being applied globally, or overridden on a per route level, such as by defining\r\n\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ]\r\n```\r\n\r\nFor the route.\r\n\r\nPer the spec at https://swagger.io/docs/specification/authentication/\r\n\r\nAs far as I can see this is not currently represeented anywhere by the component\r\n\r\n\r\n\r\nhttps://gist.github.com/addshore/e6b973939739e25902025bf1667e69a1 is an example API spec that demonstrates this feature and thus issue",[3068,3071],{"name":3069,"color":3070},"enhancement","a2eeef",{"name":3072,"color":3073},"help wanted","008672","Support security schema rendering","2024-08-30T22:52:04Z","https://github.com/enzonotario/vitepress-openapi/issues/12",{"description":3078,"labels":3079,"number":3081,"owner":3020,"repository":3021,"state":3031,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### 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",[3080],{"name":3069,"color":3070},120,"Add tags slot","2024-12-02T03:07:06Z","https://github.com/enzonotario/vitepress-openapi/issues/120",0.83505154,{"description":3087,"labels":3088,"number":3090,"owner":3020,"repository":3021,"state":3031,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Current behavior\n\n\n\n### Desired behavior\n\nI'm not sure what the desired behaviour should be here.\nHowever the `xxx` is seemingly hardcoded in the components currently, and i half would have expected the example to override this based on the behaviours of other parameter and variables examples in the playground.\n\nIt might even be nicer to just have the default auth actually always be an empty string rather than xxx?\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nJust provide an example, and see it not appear in the playground...\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3089],{"name":3069,"color":3070},237,"Authorization example not shown in playground, inconsistent with other examples?","2025-06-22T12:55:44Z","https://github.com/enzonotario/vitepress-openapi/issues/237",0.8402473,{"description":3096,"labels":3097,"number":3099,"owner":3020,"repository":3021,"state":3031,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### 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_",[3098],{"name":3069,"color":3070},130,"Allow multiple query param examples","2024-12-12T14:37:35Z","https://github.com/enzonotario/vitepress-openapi/issues/130",0.8468322,["Reactive",3105],{},["Set"],["ShallowReactive",3108],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fcM0gm5pbsJwVFgqO5Tqs6gFucQFFVLkj3Haj1QVFA0Q":-1},"/enzonotario/lighthouse-laravel-websockets/30"]