\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,"enzonotario","vitepress-openapi","closed","[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.7861991,{"description":3028,"labels":3029,"number":3033,"owner":3020,"repository":3021,"state":3022,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### What would you like?\n\nI'd love it if there was an easy to use component that allowed displaying a link that looked like the nice fancy sidebars\n\nThis should be documented\n\n\n\nI'd like to be able to use this anywhere in text\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_",[3030],{"name":3031,"color":3032},"enhancement","a2eeef",222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.78833413,{"description":3039,"labels":3040,"number":3042,"owner":3020,"repository":3021,"state":3022,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### What would you like?\n\nThe current version generates \"static\" code for each language, based only on the url and method. Unfortunately, the url is simply: `const url = props.baseUrl + props.path`. This has the issue that any path parameters are left as-is in the code.\r\n\r\nIt would be great if the sample code could be updated to include the variables in the \"try it\" box. This way the code sample would be \"complete\". I _think_ this would be done in much the same was as the `OACodeBlock` currently computes the URL for curl\n\n### Why is this needed?\n\nIf you copy-and-paste the code sample as-is, you will end up with an invalid URL if there are path parameters.\r\n\r\nAlso, it would be nice to mix-and-match such that you can _remove_ the try it portion of the playground, but keep the sample code. This way people can \"build\" a request in their language of choice based on the variables form.\n\n### How could it be implemented?\n\nI _think_ you would need to extract (or just duplicate?) the code used to compute the curl information:\r\n\r\n```\r\nconst curl = computed(() => {\r\n const headers = request.value.headers\r\n if (!headers?.['Content-Type']) {\r\n headers['Content-Type'] = 'application/json'\r\n }\r\n\r\n return fetchToCurl({\r\n method: props.method.toUpperCase(),\r\n url: request.value.url,\r\n headers,\r\n body: request.value.body ? formatJson(request.value.body) : null,\r\n })\r\n})\r\n```\r\n\r\nThen pass this as a parameter to `generateCodeSamples` so that it can generate each code sample appropriately.\n\n### Other information\n\nIt would also be _awesome_ to select _which_ languages you want to support, and possibly even some way to provide the template for each language. I realize this is above-and-beyond, but something to think about if you're changing this.",[3041],{"name":3031,"color":3032},92,"Modify Sample Code Based on Variables","2024-11-15T02:40:07Z","https://github.com/enzonotario/vitepress-openapi/issues/92",0.79363847,{"description":3048,"labels":3049,"number":3050,"owner":3020,"repository":3051,"state":3022,"title":3052,"updated_at":3053,"url":3054,"score":3055},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],40,"esjs-dolar-api","H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.79417145,{"description":3057,"labels":3058,"number":3062,"owner":3020,"repository":3051,"state":3022,"title":3063,"updated_at":3064,"url":3065,"score":3066},"Current data is wrong. Values are just NULL\r\n\r\nhttps://ve.dolarapi.com/v1/dolares/paralelo\r\n\r\nResponse:\r\n```JSON\r\n{\r\n\"fuente\": \"paralelo\",\r\n\"nombre\": \"Paralelo\",\r\n\"compra\": null,\r\n\"venta\": null,\r\n\"promedio\": 0,\r\n\"fechaActualizacion\": \"2024-10-18T14:00:33.505Z\"\r\n}\r\n```",[3059],{"name":3060,"color":3061},"venezuela","3FB1EC",30,"VE paralelo responds null","2024-10-19T02:46:03Z","https://github.com/enzonotario/esjs-dolar-api/issues/30",0.8064522,{"description":3068,"labels":3069,"number":3071,"owner":3020,"repository":3021,"state":3022,"title":3072,"updated_at":3073,"url":3074,"score":3075},"The generated example code looks like this...\n\n```\ncurl 'https://api.foo/v2/devices/%7Bid%7D/tags' \\\n --header 'Authorization: xxx'\n```\n\nHowever really in the UI it would be nicer to look like\n\n```\ncurl 'https://api.foo/v2/devices/{id}/tags' \\\n --header 'Authorization: xxx'\n```",[3070],{"name":3031,"color":3032},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.81721044,{"description":3077,"labels":3078,"number":3079,"owner":3020,"repository":3021,"state":3022,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### 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.8183099,{"description":3085,"labels":3086,"number":3090,"owner":3020,"repository":3051,"state":3022,"title":3091,"updated_at":3092,"url":3093,"score":3094},"```\r\n{\r\n\t\"moneda\": \"USD\",\r\n\t\"casa\": \"bolsa\",\r\n\t\"nombre\": \"Bolsa\",\r\n\t\"compra\": 128350,\r\n\t\"venta\": 128940,\r\n\t\"fechaActualizacion\": \"2024-09-03T12:57:00.000Z\"\r\n}\r\n```\r\n\r\nLuego de varios intentos de request por distintos medios, recibo la respuesta de los valores sin decimales tal como se ve en el ejemplo.\r\n\r\nLa respuesta que ofrece la API es correcta y debo dividir por 100 para obtener los decimales o es un bug a corregir?",[3087],{"name":3088,"color":3089},"bug","d73a4a",28,"Dolar bolsa valores sin decimales ","2024-09-03T14:53:10Z","https://github.com/enzonotario/esjs-dolar-api/issues/28",0.8194938,{"description":3096,"labels":3097,"number":3098,"owner":3020,"repository":3021,"state":3022,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### 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.8208183,{"description":3104,"labels":3105,"number":3106,"owner":3020,"repository":3021,"state":3022,"title":3107,"updated_at":3108,"url":3109,"score":3110},"I noticed this while playing with the auth tokens, however it probably applies to all fields.\n\nIt would be really nice while clicking into a field that has `.` chars in it, if by default it would select the whole field?\n\n\n\nFor this token, it breaks on the 2 `.` sections",[],247,"Change field selection boundaries","2025-06-26T22:32:02Z","https://github.com/enzonotario/vitepress-openapi/issues/247",0.8216298,["Reactive",3112],{},["Set"],["ShallowReactive",3115],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fI05nKux6DBEEOEwHr3qBrW3IoUVuZKHk8pS6I23skhY":-1},"/enzonotario/vitepress-openapi/37"]