\n \u003C/details>\n \u003C/template>\n\u003C/OAOperation>\n```\n\nBut cannot figure out where to import `OAParameters` component from...\nBecause getting error: `Vue warn]: Failed to resolve component: OAParameters`",[],290,"How to make Operation parameters collapsible/expandable?","2025-08-08T16:06:36Z","https://github.com/enzonotario/vitepress-openapi/issues/290",0.7872516,{"description":3200,"labels":3201,"number":3203,"owner":3172,"repository":3173,"state":3186,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### What would you like?\n\nlanguage add chinese\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_",[3202],{"name":3183,"color":3184},235,"language add chinese","2025-06-30T01:20:37Z","https://github.com/enzonotario/vitepress-openapi/issues/235",0.7913138,{"description":3209,"labels":3210,"number":3212,"owner":3172,"repository":3173,"state":3186,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### 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",[3211],{"name":3183,"color":3184},120,"Add tags slot","2024-12-02T03:07:06Z","https://github.com/enzonotario/vitepress-openapi/issues/120",0.7973876,{"description":3218,"labels":3219,"number":3224,"owner":3172,"repository":3173,"state":3186,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### 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_",[3220,3223],{"name":3221,"color":3222},"documentation","0075ca",{"name":3183,"color":3184},174,"[Feature]: Set `OAOperation` default `schema` or `json` and collapsed","2025-02-19T23:14:42Z","https://github.com/enzonotario/vitepress-openapi/issues/174",0.80433327,{"description":3230,"labels":3231,"number":3232,"owner":3172,"repository":3173,"state":3186,"title":3233,"updated_at":3234,"url":3235,"score":3236},"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.8102618,{"description":3238,"labels":3239,"number":2407,"owner":3172,"repository":3240,"state":3186,"title":3241,"updated_at":3242,"url":3243,"score":3244},"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?",[],"lighthouse-laravel-websockets","Subscription","2020-11-07T13:39:54Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/12",0.81569266,{"description":3246,"labels":3247,"number":2407,"owner":3172,"repository":3173,"state":3186,"title":3252,"updated_at":3253,"url":3254,"score":3244},"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",[3248,3249],{"name":3183,"color":3184},{"name":3250,"color":3251},"help wanted","008672","Support security schema rendering","2024-08-30T22:52:04Z","https://github.com/enzonotario/vitepress-openapi/issues/12",{"description":3256,"labels":3257,"number":3261,"owner":3172,"repository":3173,"state":3186,"title":3262,"updated_at":3263,"url":3264,"score":3265},"### What would you like?\n\nWould it be possible to have a loading indicator for the content?\n\n### Why is this needed?\n\nWhen a user clicks the API button on my documentation, nothing happens for a second or two while the content loads, then the page changes to show the API content.\n\nThis may be related to #171.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3258],{"name":3259,"color":3260},"needs reproduction","ffffff",241,"Loading indicator","2025-06-30T01:30:42Z","https://github.com/enzonotario/vitepress-openapi/issues/241",0.8197306,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fK9jX1UWb8uJBFC_mt5vSX_Sb_aertQ1AeHki2ovD3fc":-1},"/enzonotario/vitepress-openapi/229"]