\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_",[3181],{"name":3182,"color":3183},"needs reproduction","ffffff",278,"vitepress-openapi","Shiki instance not being reused","2025-09-11T11:47:16Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.7999706,{"description":3191,"labels":3192,"number":3193,"owner":3171,"repository":3185,"state":3173,"title":3194,"updated_at":3195,"url":3196,"score":3197},"### Current behavior\n\n`isDark` is not working when using `apparance: 'force-dark'`\n\n### Desired behavior\n\n`isDark = true` when using `apparance: 'force-dark'`\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nSet `apparance: 'force-dark'` in `.vitepress/config.js`\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\nIt's because we are now trying to get `isDark` from the `useData` VitePress composable. However there is a pending issue for this: https://github.com/vuejs/vitepress/pull/4509\n\nDue to this, we are currently retrieving `isDark` from `@vueuse/core`, but it doesn't work when using `apparance: 'force-dark'`.\n\nA workaround would be to allow forcing `isDark` prop from Feature Components.",[],178,"`isDark` is not working when using `apparance: 'force-dark'`","2025-02-17T02:26:34Z","https://github.com/enzonotario/vitepress-openapi/issues/178",0.83135545,{"description":3199,"labels":3200,"number":3201,"owner":3171,"repository":3185,"state":3173,"title":3202,"updated_at":3203,"url":3204,"score":3205},"When specifying filters like this\n\n```\n 'filter': [\n {\"limit\":10,\"order\":[\"timestamp DESC\"]},\n {\"where\":{\"type\":\"temp\"},\"limit\":10,\"order\":[\"timestamp DESC\"]},\n {\"where\":{\"type\":\"temp\",\"timestamp\":{\"between\":[\"2024-12-01T00:00:00.000Z\",\"2024-12-01T23:59:59.999Z\"]}},\"order\":[\"timestamp DESC\"]},\n ],\n```\n\nExamples are displayed like this\n\n\u003Cimg width=\"1517\" height=\"174\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/16204d6a-a65b-4dce-b272-92548870deea\" />\n\nWhich looks nice, and is copyable in the left-hand side, however the right hand side syas [object Obvject] etc...\n\n---------------\n\nWhen specifying strings of json as the filters like this\n\n```\n 'filter': [\n '{\"limit\":10,\"order\":[\"timestamp DESC\"]}',\n '{\"where\":{\"timestamp\":{\"between\":[\"2024-12-01T00:00:00.000Z\",\"2024-12-01T23:59:59.999Z\"]}},\"order\":[\"timestamp DESC\"]}',\n '{\"where\":{\"correlationId\":\"abc123\"}}',\n ],\n```\n\nWe get an ugly left-hand side with escaping, and a nice right-hand side placeholder (no extra escaping)\n\n\u003Cimg width=\"1509\" height=\"220\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a411efc1-f555-4d69-abb3-0dab9ee25450\" />\n\nUltimately in one of these cases, I would like the left-hand side to have a copyable string without escaping of \", and in the right-hand side it still be shown nicely in the placeholder.",[],301,"Consistently handle example json escaping","2025-08-28T15:58:55Z","https://github.com/enzonotario/vitepress-openapi/issues/301",0.83375514,{"description":3207,"labels":3208,"number":3209,"owner":3171,"repository":3185,"state":3210,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### 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,"closed","Pages by Operation Example dose not work","2025-04-30T22:18:57Z","https://github.com/enzonotario/vitepress-openapi/issues/212",0.7591612,{"description":3216,"labels":3217,"number":1672,"owner":3171,"repository":3218,"state":3210,"title":3219,"updated_at":3220,"url":3221,"score":3222},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],"esjs-dolar-api","H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.76996154,{"description":3224,"labels":3225,"number":3226,"owner":3171,"repository":3185,"state":3210,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Current behavior\n\nFirst of all, thank you for this fantastic theme/addon!\n\nWe are using multiple root levels in our vitepress API (`/api/` and `/sdk/`, etc.) like this. Openapi link generation works, however this way openapi links are not auto activated anymore when clicked or scrolled. \n\n### Desired behavior\n\nSidebar links are marked as active on click or hover.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-2k5lx5mk\n\n### Steps to reproduce\n\n```js\n themeConfig: {\n sidebar: {\n '/api/': {\n base: '/api/',\n items: [\n {\n text: 'API Documentation',\n items: [\n {text: 'Quickstart', link: 'quickstart'},\n ]\n },\n {\n text: 'By Tags',\n items: [\n ...sidebar.itemsByTags(),\n ],\n },\n {\n text: 'By Operations',\n items: [\n ...sidebar.generateSidebarGroups(),\n ],\n }\n ]\n },\n '/sdk/': {\n base: '/sdk/',\n items: [\n {\n text: 'SDK Documentation',\n items: [\n {text: 'Getting Started', link: 'getting-started'},\n ]\n }\n ]\n }\n }\n }\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[],213,"Sidebar items not activating when using base in parent in sidebar","2025-05-01T22:37:29Z","https://github.com/enzonotario/vitepress-openapi/issues/213",0.79407525,{"description":3232,"labels":3233,"number":3237,"owner":3171,"repository":3185,"state":3210,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Current behavior\n\nI installed the newest version of vitepress-openapi, but my Gitlab runner doesn't know what a **File** is, before this update that wasn't a problem.\n\n\u003Cimg width=\"1015\" height=\"171\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/14b865c3-be33-4ce1-9979-30a4cfdf80e4\" />\n\nThis is the code that crashes the runner\n\n\u003Cimg width=\"743\" height=\"433\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1cc2321d-05e5-4e0a-9e2f-f0846ea8042a\" />\n\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nInstall latest version of vitepress-openapi\nTry to build it with Gitlab Runner\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3234],{"name":3235,"color":3236},"bug","d73a4a",303,"Newest release breaks Gitlab runner","2025-09-15T09:29:46Z","https://github.com/enzonotario/vitepress-openapi/issues/303",0.8007641,{"description":3243,"labels":3244,"number":3248,"owner":3171,"repository":3185,"state":3210,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### Current behavior\n\n[plugin:vite:import-analysis] Failed to resolve import \"vitepress-openapi/client\" from \".vitepress/theme/index.ts\". Does the file exist?\n\n\n```\n~/demo2/.vitepress/theme/index.ts:1:44\n1 | import { theme, useOpenapi, useShiki } from \"vitepress-openapi/client\";\n | ^\n2 | import DefaultTheme from \"vitepress/theme\";\n3 | import spec from \"../../public/openapi.json\" with { type: \"json\" };\n```\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\ngit clone https://github.com/enzonotario/vitepress-openapi\ncd vitepress-openapi\ncp -r docs ~/demos\n```\n\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3245],{"name":3246,"color":3247},"question","d876e3",208,"init error","2025-04-20T13:05:55Z","https://github.com/enzonotario/vitepress-openapi/issues/208",0.8022133,{"description":3254,"labels":3255,"number":3256,"owner":3171,"repository":3185,"state":3210,"title":3257,"updated_at":3258,"url":3259,"score":3260},"Hi! I was working on my current project, where I have a schema that produces this UI:\n\nhttps://github.com/user-attachments/assets/21f90ff1-fb58-4aff-86e5-249e453c829f\n\nThis little screencast aims to show that it's a bit non-obvious - especially for people who are just starting to explore the site with the spec and don't know how the UI works - that object properties are there. Long description with some markdown/emojis makes it seem like the description is all that exists under this property.\n\nIn contrast, when there's no description, it's pretty obvious that the properties are expandable:\n\n\u003Cimg width=\"390\" height=\"113\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5b945a5a-e471-44b3-8f18-0e0219c8caa0\" />\n\nBut in the case of a rich description - which is visible by default and draws attention away from the relatively small \"expand\" button icon on the top - a user who reads the description might reasonably assume that it's the only content. They may not think, \"Hmm, I read the description, but there must be properties - let me look for some element that will let me show them!\"\n\n## Suggestions:\n\n### Option 1:\n\nHide descriptions for objects when in Collapsed state, show only when Expanded:\n\nhttps://github.com/user-attachments/assets/40ead49f-6023-4cbb-9a7b-8e5a5c96b952\n\n### Option 2:\n\nShow a small hint after the description, like a verbose \"Expand\" text button or a similar UI element (only shown when it's an array/object and has a description):\n\nhttps://github.com/user-attachments/assets/c8a31a05-6b54-400d-84a9-b126b9762b1e\n\n---\n\nLet me know what you think, @enzonotario! Do you like any of the proposed options, or do you have some other idea of how to address this?",[],271,"[Discussion] When an object has a description, it's not obvious that its properties are expandable","2025-07-21T01:18:22Z","https://github.com/enzonotario/vitepress-openapi/issues/271",0.8042486,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$frN-1JaZVlCBS9L36iZkmEQXWYnjTL_Wdyk6AYTTRFCE":-1},"/enzonotario/vitepress-openapi/251"]