\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.86042345,{"description":3036,"labels":3037,"number":3038,"owner":3020,"repository":3021,"state":3039,"title":3040,"updated_at":3041,"url":3042,"score":3043},"Tried on 0.0.3-alpha.63, and 0.0.3-alpha.79 (latest release)\n\nI have a header such as this defined\n\n```\n {\n \"description\": \"Optionally provide parameters as a JSON object in this header. If both query params and X-Query overlap, a 400 error is returned.\",\n \"example\": \"{\\\"id\\\":\\\"1\\\"}\",\n \"in\": \"header\",\n \"name\": \"X-Query\",\n \"schema\": {\n \"type\": \"string\"\n }\n }\n```\n\nBut also a param like this\n\n```\n {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"in\": \"query\",\n \"name\": \"id\",\n \"schema\": {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"example\": \"1\",\n \"form\": \"id\",\n \"type\": \"string\"\n }\n },\n```\n\nBoth of these examples are used by the UI component, and provided in the default try it requests.\nHowever this means that the request will always fail, as the examples conflict with each other.\nHowever, I want to be able to provide real examples to both of these...\n\nI think that either\n1) Examples should not be used in the default try it param\n2) There should be an option to disable it?",[],221,"closed","example should not always be used as the default for the UI","2025-05-18T01:43:41Z","https://github.com/enzonotario/vitepress-openapi/issues/221",0.78643143,{"description":3045,"labels":3046,"number":3050,"owner":3020,"repository":3051,"state":3039,"title":3052,"updated_at":3053,"url":3054,"score":3055},"Hola Enzo, espero que andes bien.\r\n\r\nVeo que la API está devolviendo precio de venta 1 para el dólar mayorista a partir del día 23/10/2024. ¿Por qué puede ser?\r\n\r\n {\r\n \"casa\": \"mayorista\",\r\n \"compra\": 962.57,\r\n \"venta\": 1,\r\n \"fecha\": \"2024-10-23\"\r\n },\r\n {\r\n \"casa\": \"mayorista\",\r\n \"compra\": 962.57,\r\n \"venta\": 1,\r\n \"fecha\": \"2024-10-24\"\r\n },\r\n {\r\n \"casa\": \"mayorista\",\r\n \"compra\": 962.57,\r\n \"venta\": 1,\r\n \"fecha\": \"2024-10-25\"\r\n }\r\n\r\nSaludos\r\nDamian.",[3047],{"name":3048,"color":3049},"bug","d73a4a",8,"esjs-argentina-datos-api","Dolar Venta Mayorista en 1","2024-11-01T03:00:22Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/8",0.7959077,{"description":3057,"labels":3058,"number":3062,"owner":3020,"repository":3021,"state":3039,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### What would you like?\n\nI wonder if it is possible to implement path based sidebar. For example, we have\r\n\r\n```\r\n/api/v1/products CRUD\r\n/api/v1/orders CRUD\r\n```\r\n\r\nSidebar would look like\r\n\r\n```\r\n/api/v1\r\n ├ products\r\n | ├ PUT\r\n | ├ GET\r\n | ├ POST\r\n | └ DELETE\r\n └ orders\r\n ├ PUT\r\n ├ GET\r\n ├ POST\r\n └ DELETE\r\n```\r\n\r\n**Note**: empty folders are collapsed\r\n\n\n### Why is this needed?\n\nI want to use more than one tag per endpoint. But in this case sidebar looks strange. Maybe there is a way to organize sidebar better even if there are multiple tags...\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3059],{"name":3060,"color":3061},"enhancement","a2eeef",119,"Path based sidebar","2024-12-12T03:25:21Z","https://github.com/enzonotario/vitepress-openapi/issues/119",0.7984751,{"description":3068,"labels":3069,"number":3070,"owner":3020,"repository":3071,"state":3039,"title":3072,"updated_at":3073,"url":3074,"score":3075},"Buenas! Qué tal?\r\n\r\nEstoy viendo un error en la cotización del Peso Chileno, probablemente relacionado con otro issue cerrado que leí recién, donde el valor hay que dividirlo por 100 para que esté bien. Esto es lo que está mostrando ahora:\r\n\r\n\r\n\r\nMil gracias por API!!\r\nSaludos!\r\n\r\n",[],29,"esjs-dolar-api","Error en la cotización del Peso Chileno","2024-09-06T21:40:13Z","https://github.com/enzonotario/esjs-dolar-api/issues/29",0.8010138,{"description":3077,"labels":3078,"number":3079,"owner":3020,"repository":3021,"state":3039,"title":3080,"updated_at":3081,"url":3082,"score":3083},"I noticed this while playing with the auth tokens, however it probably applies to all fields.\n\nIt would be really nice while clicking into a field that has `.` chars in it, if by default it would select the whole field?\n\n\n\nFor this token, it breaks on the 2 `.` sections",[],247,"Change field selection boundaries","2025-06-26T22:32:02Z","https://github.com/enzonotario/vitepress-openapi/issues/247",0.82172114,{"description":3085,"labels":3086,"number":3087,"owner":3020,"repository":3021,"state":3039,"title":3088,"updated_at":3089,"url":3090,"score":3091},"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.82701224,{"description":3093,"labels":3094,"number":3096,"owner":3020,"repository":3021,"state":3039,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### 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",[3095],{"name":3060,"color":3061},120,"Add tags slot","2024-12-02T03:07:06Z","https://github.com/enzonotario/vitepress-openapi/issues/120",0.82970726,{"description":3102,"labels":3103,"number":3105,"owner":3020,"repository":3021,"state":3039,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Current behavior\n\nOn some route, the schema view is empty even though the json view is not\n\n### Desired behavior\n\nI expect the schema view to always represent the type\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/post-api-scheduling-scheduleExecution.html\r\n# click on Schema view for Request Body, see it is empty\r\n```\r\n\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3104],{"name":3048,"color":3049},110,"Schema view empty even though json view is not","2024-11-30T14:09:26Z","https://github.com/enzonotario/vitepress-openapi/issues/110",0.83888966,["Reactive",3111],{},["Set"],["ShallowReactive",3114],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fk1yBgMVZGlJFgAr2od3SO1Q34t31aMYvIpwJEUjLK3Y":-1},"/enzonotario/vitepress-openapi/109"]