\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.81714803,{"description":3067,"labels":3068,"number":1024,"owner":3019,"repository":3020,"state":3042,"title":3070,"updated_at":3071,"url":3072,"score":3073},"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? :)",[3069],{"name":3039,"color":3040},"Enable rendering components for multiple specs on a single page.","2024-09-28T15:44:23Z","https://github.com/enzonotario/vitepress-openapi/issues/21",0.83056056,{"description":3075,"labels":3076,"number":3081,"owner":3019,"repository":3020,"state":3042,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### What would you like?\n\nRight now It generate such page \r\n\r\n\r\nwould like to remove Default on the side and move the table of content to the left\r\n\r\nOr alternatively, if I could change the name and add a description so the left do not feel emptu\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_",[3077,3078],{"name":3039,"color":3040},{"name":3079,"color":3080},"question","d876e3",109,"Any way to remove default or change the name and add description","2024-11-03T03:36:50Z","https://github.com/enzonotario/vitepress-openapi/issues/109",0.83372664,{"description":3087,"labels":3088,"number":104,"owner":3019,"repository":3090,"state":3042,"title":3091,"updated_at":3092,"url":3093,"score":3094},"Sugiero que la API retorne cotizaciones del día anterior, de esa manera se puede calcular fácilmente las variaciones porcentuales.\r\n\r\nEjemplo:\r\n\r\n```\r\n[\r\n \"Hoy\": {\r\n \"compra\": \"number\",\r\n \"venta\": \"number\",\r\n \"casa\": \"string\",\r\n \"nombre\": \"string\",\r\n \"moneda\": \"string\",\r\n \"fechaActualizacion\": \"string\"\r\n },\r\n \"Ayer\": {\r\n \"compra\": \"number\",\r\n \"venta\": \"number\",\r\n \"casa\": \"string\",\r\n \"nombre\": \"string\",\r\n \"moneda\": \"string\",\r\n \"fechaActualizacion\": \"string\"\r\n }\r\n]\r\n```",[3089],{"name":3039,"color":3040},"esjs-dolar-api","[New Feature] Añadir cotización del día anterior","2024-01-31T23:06:14Z","https://github.com/enzonotario/esjs-dolar-api/issues/3",0.8373117,{"description":3096,"labels":3097,"number":104,"owner":3019,"repository":3020,"state":3042,"title":3098,"updated_at":3099,"url":3100,"score":3094},"> operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API.\r\n\r\nAs a result my spec doesnt actually have `operationId` in it for each route\r\nIt would be great if route and method could be used in combination insead of operationId :)",[],"Allow selection by path / key as well as / insead of operationId ?","2024-08-27T23:04:25Z","https://github.com/enzonotario/vitepress-openapi/issues/3",{"description":3102,"labels":3103,"number":3104,"owner":3019,"repository":3020,"state":3042,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### What would you like?\n\nSwagger-ui has the option to set a token once for the site and have it be used for every test api call. Maybe such an option would also be nice for the openapi theme.\n\n### Why is this needed?\n\nMakes it a bit friendlier to use as you do not need to constantly insert a bearer token.\n\n### How could it be implemented?\n\nSimilarly to how swagger-ui does it. Have a global button which stores the authentication method / value.\n\n### Other information\n\n_No response_",[],59,"[Feature] Site-wide authentication","2024-09-29T13:52:47Z","https://github.com/enzonotario/vitepress-openapi/issues/59",0.8478105,["Reactive",3110],{},["Set"],["ShallowReactive",3113],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2vqVQ8tDGbynF98i_QZimvr-UQp-CJ8_c9ERe76b_6w":-1},"/enzonotario/vitepress-openapi/110"]