\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_",[3239],{"name":3240,"color":3241},"bug","d73a4a",303,"Newest release breaks Gitlab runner","2025-09-15T09:29:46Z","https://github.com/enzonotario/vitepress-openapi/issues/303",0.8096262,{"description":3248,"labels":3249,"number":3251,"owner":3172,"repository":3173,"state":3211,"title":3252,"updated_at":3253,"url":3254,"score":3255},"Especifico el tipo de respuesta que retornara la petición, pero lo toma como un objeto.\r\n\r\n--\r\n\r\n",[3250],{"name":3208,"color":3209},33,"Tipo de respuesta ","2024-09-26T23:34:06Z","https://github.com/enzonotario/vitepress-openapi/issues/33",0.8105178,{"description":3257,"labels":3258,"number":3259,"owner":3172,"repository":3173,"state":3211,"title":3260,"updated_at":3261,"url":3262,"score":3263},"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,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSBkjiyZhvx9xbOtogEK8Otz1RSC8uZJzy4N-3npPxgY":-1},"/enzonotario/vitepress-openapi/120"]