\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,"vitepress-openapi","Shiki instance not being reused","2025-07-20T22:19:25Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.8531251,{"description":3037,"labels":3038,"number":3045,"owner":3020,"repository":3031,"state":3046,"title":3047,"updated_at":3048,"url":3049,"score":3050},"### 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_",[3039,3042],{"name":3040,"color":3041},"documentation","0075ca",{"name":3043,"color":3044},"enhancement","a2eeef",174,"closed","[Feature]: Set `OAOperation` default `schema` or `json` and collapsed","2025-02-19T23:14:42Z","https://github.com/enzonotario/vitepress-openapi/issues/174",0.751383,{"description":3052,"labels":3053,"number":3057,"owner":3020,"repository":3031,"state":3046,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Current behavior\n\nWhen i have the following JSON \n`{\n \"openapi\": \"3.0.0\",\n \"info\": {\n \"title\": \"API with X-Api-Key Authentication\",\n \"version\": \"1.0.0\"\n },\n \"components\": {\n \"securitySchemes\": {\n \"ApiKeyAuth\": {\n \"type\": \"apiKey\",\n \"in\": \"header\",\n \"name\": \"X-Api-Key\"\n }\n }\n },\n \"paths\": {\n \"/protected-endpoint\": {\n \"get\": {\n \"summary\": \"An endpoint requiring X-Api-Key\",\n \"security\": [\n {\n \"ApiKeyAuth\": []\n }\n ],\n \"responses\": {\n \"200\": {\n \"description\": \"Success\"\n },\n \"401\": {\n \"description\": \"Unauthorized\"\n }\n }\n }\n }\n }\n}`\n\nit shows \n\n\nIn the samples.\n\n### Desired behavior\n\n\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nhttps://docs.xs2event.com/operations/bookings_get.html\n\nhttps://docs.xs2event.com/assets/openapi.json\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3054],{"name":3055,"color":3056},"bug","d73a4a",168,"Headers are passed wrong to Samples","2025-02-03T01:59:38Z","https://github.com/enzonotario/vitepress-openapi/issues/168",0.7866749,{"description":3063,"labels":3064,"number":3065,"owner":3020,"repository":3031,"state":3046,"title":3066,"updated_at":3067,"url":3068,"score":3069},"",[],124,"for `oneOf`, it seems vitepress-openapi only show the first possible type","2024-11-30T13:53:40Z","https://github.com/enzonotario/vitepress-openapi/issues/124",0.79388523,{"description":3071,"labels":3072,"number":3077,"owner":3020,"repository":3031,"state":3046,"title":3078,"updated_at":3079,"url":3080,"score":3081},"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",[3073,3074],{"name":3040,"color":3041},{"name":3075,"color":3076},"question","d876e3",195,"Collapsible operation grouping in the sidebar","2025-04-08T21:55:25Z","https://github.com/enzonotario/vitepress-openapi/issues/195",0.81124294,{"description":3083,"labels":3084,"number":3085,"owner":3020,"repository":3021,"state":3046,"title":3086,"updated_at":3087,"url":3088,"score":3089},"after running `composer-update` and install `redis`, in first serve the application i get this error on console:\r\n\r\n```\r\nGraphQL execution errors for subscription 'subscribed'\r\n\r\n\r\nObject { debugMessage: \"Connection refused\", message: \"Internal server error\", extensions: {…}, locations: (1) […], path: (1) […], trace: (63) […] }\r\n\r\ndebugMessage: \"Connection refused\"\r\n\r\nextensions: Object { category: \"internal\" }\r\n\r\nlocations: Array [ {…} ]\r\n\r\nmessage: \"Internal server error\"\r\n\r\npath: Array [ \"test\" ]\r\n\r\ntrace: Array(63) [ {…}, {…}, {…}, … ]\r\n\r\n\u003Cprototype>: Object { … }\r\n```\r\n\r\nhow can i resolve this problem? thanks in advance",[],30,"Getting error on first serve sample","2021-11-08T00:33:32Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/30",0.81471056,{"description":3091,"labels":3092,"number":2391,"owner":3020,"repository":3021,"state":3046,"title":3093,"updated_at":3094,"url":3095,"score":3096},"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.81661123,{"description":3098,"labels":3099,"number":2391,"owner":3020,"repository":3031,"state":3046,"title":3104,"updated_at":3105,"url":3106,"score":3096},"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",[3100,3101],{"name":3043,"color":3044},{"name":3102,"color":3103},"help wanted","008672","Support security schema rendering","2024-08-30T22:52:04Z","https://github.com/enzonotario/vitepress-openapi/issues/12",{"description":3108,"labels":3109,"number":3110,"owner":3020,"repository":3031,"state":3046,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### 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.83663267,["Reactive",3116],{},["Set"],["ShallowReactive",3119],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJqGqIKWzQrfFKs6CwpyHrbC3qa0uArXFsdjdv3DA9ME":-1},"/enzonotario/lighthouse-laravel-websockets/1"]