\n\n \n\n### Desired behavior\n\nShiki should be initialized once and reused for subsequent highlight calls.\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nLoad a large vitepress project with any code in it\n\n### Logs and Error Messages\n\nvitepress-openapi.client.es.js:62532 [Shiki] 590 instances have been created. Shiki is supposed to be used as a singleton, consider refactoring your code to cache your highlighter instance; Or call `highlighter.dispose()` to release unused instances.\n\n### Other Information\n\n_No response_",[],278,"enzonotario","vitepress-openapi","open","Shiki instance not being reused","2025-07-20T22:19:25Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.90289557,{"description":3028,"labels":3029,"number":734,"owner":3020,"repository":3030,"state":3031,"title":3032,"updated_at":3033,"url":3034,"score":3035},"",[],"lighthouse-laravel-websockets","closed","does it work with v4 lighthouse?","2020-11-07T13:40:11Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/2",0.4614822,{"description":3037,"labels":3038,"number":2391,"owner":3020,"repository":3030,"state":3031,"title":3039,"updated_at":3040,"url":3041,"score":3042},"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.7953467,{"description":3044,"labels":3045,"number":2391,"owner":3020,"repository":3021,"state":3031,"title":3052,"updated_at":3053,"url":3054,"score":3042},"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",[3046,3049],{"name":3047,"color":3048},"enhancement","a2eeef",{"name":3050,"color":3051},"help wanted","008672","Support security schema rendering","2024-08-30T22:52:04Z","https://github.com/enzonotario/vitepress-openapi/issues/12",{"description":3056,"labels":3057,"number":3062,"owner":3020,"repository":3021,"state":3031,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### What would you like?\n\nSet the default request and response shown of a `OAOperation` to _schema_, and also be able to collapse it, since I have some large entities.\n\n### Why is this needed?\n\nMakes large request and responses easier to work with.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3058,3061],{"name":3059,"color":3060},"documentation","0075ca",{"name":3047,"color":3048},174,"[Feature]: Set `OAOperation` default `schema` or `json` and collapsed","2025-02-19T23:14:42Z","https://github.com/enzonotario/vitepress-openapi/issues/174",0.86200064,{"description":3068,"labels":3069,"number":1443,"owner":3020,"repository":3030,"state":3031,"title":3070,"updated_at":3071,"url":3072,"score":3073},"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.8685809,{"description":3075,"labels":3076,"number":3077,"owner":3020,"repository":3021,"state":3031,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### 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.8843049,{"description":3083,"labels":3084,"number":3086,"owner":3020,"repository":3021,"state":3031,"title":3087,"updated_at":3088,"url":3089,"score":3090},"Especifico el tipo de respuesta que retornara la petición, pero lo toma como un objeto.\r\n\r\n--\r\n\r\n",[3085],{"name":3047,"color":3048},33,"Tipo de respuesta ","2024-09-26T23:34:06Z","https://github.com/enzonotario/vitepress-openapi/issues/33",0.8871675,{"description":3092,"labels":3093,"number":3098,"owner":3020,"repository":3021,"state":3031,"title":3099,"updated_at":3100,"url":3101,"score":3102},"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",[3094,3095],{"name":3059,"color":3060},{"name":3096,"color":3097},"question","d876e3",195,"Collapsible operation grouping in the sidebar","2025-04-08T21:55:25Z","https://github.com/enzonotario/vitepress-openapi/issues/195",0.8887221,{"description":3104,"labels":3105,"number":3107,"owner":3020,"repository":3021,"state":3031,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Current behavior\n\nI am using\r\n\r\n```\r\nuseTheme({\r\n\trequest: {\r\n\t\t// Set the default schema view.\r\n\t\tdefaultView: 'schema', // schema or contentType\r\n\t},\r\n});\r\n```\r\n\r\nto set the default view to schema but this does not work\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:dev\r\n# navigate to http://localhost:5173/api-all-in-one/\r\n# it still use JSON as default view\r\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3106],{"name":3059,"color":3060},107,"useTheme have no effect","2024-11-02T22:51:19Z","https://github.com/enzonotario/vitepress-openapi/issues/107",0.88906634,["Reactive",3113],{},["Set"],["ShallowReactive",3116],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f76kyN7YDbo66ncSGq19M_1hg6R9fuVkzR7rZgXKXR-Q":-1},"/enzonotario/vitepress-openapi/2"]