\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.81546295,{"description":3080,"labels":3081,"number":3083,"owner":3022,"repository":3036,"state":3024,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### What would you like?\r\n\r\nIt would be nice to have a select element that switches between request body examples.\r\nThis is possible in swagger UI, for example:\r\n\r\n\u003Cimg width=\"1672\" alt=\"Screenshot 2024-12-27 at 15 12 50\" src=\"https://github.com/user-attachments/assets/e5313373-cc8f-4027-9311-0e5d446b6027\" />\r\n\r\n\r\n\r\n### Why is this needed?\r\n\r\nThis is useful for endpoints that accept different request bodies\r\n\r\n### How could it be implemented?\r\n\r\nImplement and show a select element when examples are present in openapi.json:\r\n\r\n```\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/ExamplePost\"\r\n },\r\n \"examples\": {\r\n \"Example 1\": {\r\n \"summary\": \"Creating example 1\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\"\r\n }\r\n },\r\n \"example 2\": {\r\n \"summary\": \"Creating example 2\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\",\r\n \"phone_number\": \"123456789\"\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"required\": true\r\n },\r\n```\r\n\r\n### Other information\r\n\r\nI couldn't find this anywhere in the documentation, but if it is already possible i would like to know how. Thank you!",[3082],{"name":3033,"color":3034},141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.82204497,{"description":3089,"labels":3090,"number":644,"owner":3022,"repository":3023,"state":3024,"title":3092,"updated_at":3093,"url":3094,"score":3095},"Hola!\r\n\r\nLa documentación del endpoint [GET Dólar por casa y fecha](https://argentinadatos.com/docs/operations/get-cotizaciones-dolares-casa-fecha.html) no menciona `contadoconliqui` como un valor válido para `casa`, aunque si lo es. Adjunto fotos de los docs y del endpoint aceptando el valor.\r\n\r\n\u003Cdetails>\u003Csummary>Foto de los docs\u003C/summary>\r\n\r\n\u003Cimg width=\"1091\" alt=\"image\" src=\"https://github.com/user-attachments/assets/62e1efe3-ec78-4a22-a716-570910472dbc\">\r\n\r\n\u003C/details> \r\n\r\n\u003Cdetails>\u003Csummary>Endpoint acepta el valor\u003C/summary>\r\n\r\n\u003Cimg width=\"833\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0634a0ba-a4b4-4e17-a5fd-f3571d24a2b7\">\r\n\r\n\u003C/details> \r\n\r\nMuy buena API, gracias!",[3091],{"name":3020,"color":3021},"[Docs] Añadir CCL como valor válido para `casa` en GET Dólar por casa y fecha","2024-09-20T01:00:46Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/7",0.82710975,{"description":3097,"labels":3098,"number":1024,"owner":3022,"repository":3036,"state":3024,"title":3100,"updated_at":3101,"url":3102,"score":3103},"Currently I have something like this on a single markdown page...\r\n\r\n```\r\n\u003Cscript setup lang=\"ts\">\r\nimport { useRoute, useData } from 'vitepress'\r\nimport { useSidebar, useOpenapi } from 'vitepress-theme-openapi'\r\nimport spec from '../swagger/v2.json' with { type: 'json' }\r\nconst openapi = useOpenapi()\r\nopenapi.setSpec(spec)\r\nconst route = useRoute()\r\nconst { isDark } = useData()\r\n\u003C/script>\r\n\r\n\u003COAOperation operationId=\"post-users-login\" method=\"post\" :isDark=\"isDark\" />\r\n\u003COAOperation operationId=\"post-users-refreshToken\" method=\"post\" :isDark=\"isDark\" />\r\n```\r\n\r\nFurther down the page I would like to include a component rendered from the `../swagger/v1.json` spec, however I believe with the current setup that will not be possible.\r\n\r\nUltimately I think this will require passing the openapi into the components? :)",[3099],{"name":3033,"color":3034},"Enable rendering components for multiple specs on a single page.","2024-09-28T15:44:23Z","https://github.com/enzonotario/vitepress-openapi/issues/21",0.82963353,{"description":3105,"labels":3106,"number":3108,"owner":3022,"repository":3036,"state":3024,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### What would you like?\r\n\r\nParameter example values along with the description\r\n\r\nSo for example after I overloaded your template for this section I see this:\r\n\r\n**$filter** string\r\nExample name eq 'hello'\r\n\r\n\r\nYou can see the example [live here](https://apidev.digilean.tools/docs/operations/Boards_List) as well\r\n\r\n### Why is this needed?\r\n\r\nI see you use the example values in the playground/try it section\r\n\r\nBut I choose not to display this.\r\n\r\n### How could it be implemented?\r\n\r\nSomething like \r\n```vue\r\n\u003Cdiv v-if=\"props.parameter.example\" class=\"flex flex-row space-x-2\">\r\n \u003Cspan class=\"text-sm example font-bold\">\r\n Example\r\n \u003C/span>\r\n \u003Cspan class=\"text-sm text-gray-600 dark:text-gray-300\">\r\n {{ props.parameter.example }}\r\n \u003C/span>\r\n\u003C/div>\r\n```\r\n\r\n### Other information\r\n\r\n_No response_",[3107],{"name":3033,"color":3034},93,"Display example values for Parameters","2024-10-17T08:22:46Z","https://github.com/enzonotario/vitepress-openapi/issues/93",0.8300626,["Reactive",3114],{},["Set"],["ShallowReactive",3117],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fWCodpnkQCg7t5ydRWs9wkV8DTMbPz_Uh4KHU-XJllEU":-1},"/enzonotario/criptoya-api-docs/6"]