\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.7516761,{"description":3066,"labels":3067,"number":3072,"owner":3019,"repository":3020,"state":3032,"title":3073,"updated_at":3074,"url":3075,"score":3076},"### 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_",[3068,3071],{"name":3069,"color":3070},"documentation","0075ca",{"name":3030,"color":3031},174,"[Feature]: Set `OAOperation` default `schema` or `json` and collapsed","2025-02-19T23:14:42Z","https://github.com/enzonotario/vitepress-openapi/issues/174",0.7546702,{"description":3078,"labels":3079,"number":3080,"owner":3019,"repository":3020,"state":3032,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### 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.77388275,{"description":3086,"labels":3087,"number":3088,"owner":3019,"repository":3020,"state":3032,"title":3089,"updated_at":3090,"url":3091,"score":3092},"### What would you like?\n\nThis is what I expect.\n\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_",[],227,"Is the application/x-www-form-urlencoded content type supported?","2025-05-29T23:41:20Z","https://github.com/enzonotario/vitepress-openapi/issues/227",0.7824287,{"description":3094,"labels":3095,"number":1596,"owner":3019,"repository":3020,"state":3032,"title":3097,"updated_at":3098,"url":3099,"score":3100},"So, hvaing this in the front matter\r\n\r\n```\r\naside: true\r\noutline: true\r\n``` \r\n\r\nout of the box results in a very verbose set of headings.\r\n\r\nIt might be nice for the default heading levels (or tags used) to present themselves a little nicer in the asied outline!\r\n\r\n\r\n",[3096],{"name":3030,"color":3031},"Allow choosing component heading levels","2024-09-19T22:35:35Z","https://github.com/enzonotario/vitepress-openapi/issues/37",0.7842464,{"description":3102,"labels":3103,"number":3107,"owner":3019,"repository":3020,"state":3032,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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_",[3104],{"name":3105,"color":3106},"needs reproduction","ffffff",241,"Loading indicator","2025-06-30T01:30:42Z","https://github.com/enzonotario/vitepress-openapi/issues/241",0.7905029,["Reactive",3113],{},["Set"],["ShallowReactive",3116],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBTtexPCpMIpENPQuPcv4qdrQjh0AlOa-RaUoAov0Ens":-1},"/enzonotario/vitepress-openapi/222"]