\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":3211,"labels":3212,"number":1028,"owner":3172,"repository":3173,"state":3186,"title":3214,"updated_at":3215,"url":3216,"score":3217},"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? :)",[3213],{"name":3183,"color":3184},"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":3219,"labels":3220,"number":3225,"owner":3172,"repository":3173,"state":3186,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### 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_",[3221,3222],{"name":3183,"color":3184},{"name":3223,"color":3224},"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":3231,"labels":3232,"number":104,"owner":3172,"repository":3234,"state":3186,"title":3235,"updated_at":3236,"url":3237,"score":3238},"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```",[3233],{"name":3183,"color":3184},"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":3240,"labels":3241,"number":104,"owner":3172,"repository":3173,"state":3186,"title":3242,"updated_at":3243,"url":3244,"score":3238},"> 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":3246,"labels":3247,"number":3248,"owner":3172,"repository":3173,"state":3186,"title":3249,"updated_at":3250,"url":3251,"score":3252},"I believe spec such as this is valid and OK.\n\nBasically having a schema object, that has a property of type string, and then using oneOf to be abe to define extra information about the strings.\n\n```\n \"notificationTrigger\": {\n \"properties\": {\n \"name\": {\n \"type\": \"string\"\n },\n \"type\": {\n \"type\": \"string\",\n \"oneOf\": [\n { \"const\": \"lowBat\", \"title\": \"Low Battery\", \"description\": \"Triggered when battery level is low.\" },\n { \"const\": \"button\", \"title\": \"Button Press\", \"description\": \"Triggered on a button press.\" },\n \n```\n\nI believe a relevant link from the spec would be https://spec.openapis.org/oas/v3.1.1.html#model-with-annotated-enumeration\n\nHowever the components currently render this incorrectly.\n\n\u003Cimg width=\"670\" height=\"396\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/267cff6d-9c0a-4bd7-8a8e-734588fb775b\" />",[],288,"Support rendering model-with-annotated-enumeration in Request Body schema","2025-08-11T22:29:43Z","https://github.com/enzonotario/vitepress-openapi/issues/288",0.83810866,{"description":3254,"labels":3255,"number":3256,"owner":3172,"repository":3173,"state":3186,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Current behavior\n\nGiven this schema:\n```yaml\nopenapi: 3.1.0\ninfo: \n title: test\n version: '0.1'\npaths:\n /test:\n get:\n parameters:\n - in: query\n name: code\n examples:\n name_1:\n value: parameter_value_1\n name_2:\n value: parameter_value_1\n schema:\n type: string\n examples: \n - schema_value_1\n - schema_value_2\n```\n\nThe ui shows `schema_value_1` prefilled for `code` parameter which is incorrect.\n\n### Desired behavior\n\nFor GUI openapi tools `examples` from parameter object itself should be used.\nSo prefilled value should be `parameter_value_1` and not `schema_value_1`\n\nhttps://editor-next.swagger.io also uses examples from parameter object. OpenAPI specification itself does not mention `examples` under `schema` field since it is json-schema field and not OpenAPI specific field.",[],298,"`examples` field is not populated from parameter object","2025-08-27T11:00:31Z","https://github.com/enzonotario/vitepress-openapi/issues/298",0.8402448,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2vqVQ8tDGbynF98i_QZimvr-UQp-CJ8_c9ERe76b_6w":-1},"/enzonotario/vitepress-openapi/110"]