\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,"Shiki instance not being reused","2025-07-20T22:19:25Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.8313994,{"description":3052,"labels":3053,"number":3057,"owner":3019,"repository":3020,"state":3058,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### 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_",[3054],{"name":3055,"color":3056},"enhancement","a2eeef",130,"closed","Allow multiple query param examples","2024-12-12T14:37:35Z","https://github.com/enzonotario/vitepress-openapi/issues/130",0.7859832,{"description":3064,"labels":3065,"number":3067,"owner":3019,"repository":3020,"state":3058,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### What would you like?\n\nI'd love it if there was an easy to use component that allowed displaying a link that looked like the nice fancy sidebars\n\nThis should be documented\n\n\n\nI'd like to be able to use this anywhere in text\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_",[3066],{"name":3055,"color":3056},222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.79807323,{"description":3073,"labels":3074,"number":3078,"owner":3019,"repository":3020,"state":3058,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### 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_",[3075],{"name":3076,"color":3077},"question","d876e3",229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.80304426,{"description":3084,"labels":3085,"number":3087,"owner":3019,"repository":3020,"state":3058,"title":3088,"updated_at":3089,"url":3090,"score":3091},"Especifico el tipo de respuesta que retornara la petición, pero lo toma como un objeto.\r\n\r\n--\r\n\r\n",[3086],{"name":3055,"color":3056},33,"Tipo de respuesta ","2024-09-26T23:34:06Z","https://github.com/enzonotario/vitepress-openapi/issues/33",0.8105178,{"description":3093,"labels":3094,"number":3095,"owner":3019,"repository":3020,"state":3058,"title":3096,"updated_at":3097,"url":3098,"score":3099},"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.8151681,{"description":3101,"labels":3102,"number":3103,"owner":3019,"repository":3020,"state":3058,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Current behavior\n\nIn OpenAPI you can create a nullable object with:\n```yaml\ntype: [object, 'null']\nproperties:\n example:\n type: string\n```\n\nCurrently, vitepress-openapi will not display the properties correctly.\n\n### Desired behavior\n\nIf the object is nullable, it should still list all properties of nullable object and not just `object | null`\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```json\n{\n \"openapi\": \"3.1.0\",\n \"info\": {\n \"title\": \"Nullable objects\"\n },\n \"servers\": [\n {\n \"url\": \"https://whatever.com\",\n \"description\": \"Mock Server\"\n }\n ],\n \"paths\": {\n \"/nullable\": {\n \"get\": {\n \"tags\": [\n \"Nullable\"\n ],\n \"summary\": \"Get nullable object\",\n \"description\": \"Yayy\",\n \"operationId\": \"getNullableObject\",\n \"responses\": {\n \"200\": {\n \"description\": \"OK\",\n \"content\": {\n \"application/json\": {\n \"schema\": {\n \"type\": \"object\",\n \"properties\": {\n \"a\": {\n \"type\": [\n \"object\",\n \"null\"\n ],\n \"properties\": {\n \"a\": {\n \"type\": \"number\"\n }\n }\n }\n }\n }\n }\n }\n }\n }\n }\n }\n },\n \"tags\": [],\n \"externalDocs\": {}\n}\n```\n\n\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[],206,"\"nullable\" objects","2025-04-24T01:25:01Z","https://github.com/enzonotario/vitepress-openapi/issues/206",0.8160886,["Reactive",3109],{},["Set"],["ShallowReactive",3112],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSBkjiyZhvx9xbOtogEK8Otz1RSC8uZJzy4N-3npPxgY":-1},"/enzonotario/vitepress-openapi/120"]