\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","open","[Discussion] When an object has a description, it's not obvious that its properties are expandable","2025-07-15T19:05:31Z","https://github.com/enzonotario/vitepress-openapi/issues/271",0.78720355,{"description":3017,"labels":3018,"number":3022,"owner":3009,"repository":3010,"state":3023,"title":3024,"updated_at":3025,"url":3026,"score":3027},"### Current behavior\n\n\n\n### Desired behavior\n\nEither the text should wrap, or just be displayed in a better way\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\n \"securitySchemes\": {\n \"ApiKeyAuth\": {\n \"in\": \"header\",\n \"name\": \"Authorization\",\n \"type\": \"apiKey\",\n\"description\": \"API Key for authentication. Retrieval from either API version login routes, or other authentication token type. See \u003Ca href='/apis/authentication'>Authentication\u003C/a> for more details.\",\n\"example\": \"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOjEsImlhdCI6MTY3Mjc2NjAyOCwiZXhwIjoxNjc0NDk0MDI4fQ.kCak9sLJr74frSRVQp0_27BY4iBCgQSmoT3vQVWKzJg\"\n }\n }\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3019],{"name":3020,"color":3021},"bug","d73a4a",236,"closed","Long Authorization example doesnt display nicely","2025-06-22T12:55:43Z","https://github.com/enzonotario/vitepress-openapi/issues/236",0.7423333,{"description":3029,"labels":3030,"number":3034,"owner":3009,"repository":3010,"state":3023,"title":3035,"updated_at":3036,"url":3037,"score":3038},"### Current behavior\n\n\n\n### Desired behavior\n\nI'm not sure what the desired behaviour should be here.\nHowever the `xxx` is seemingly hardcoded in the components currently, and i half would have expected the example to override this based on the behaviours of other parameter and variables examples in the playground.\n\nIt might even be nicer to just have the default auth actually always be an empty string rather than xxx?\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nJust provide an example, and see it not appear in the playground...\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3031],{"name":3032,"color":3033},"enhancement","a2eeef",237,"Authorization example not shown in playground, inconsistent with other examples?","2025-06-22T12:55:44Z","https://github.com/enzonotario/vitepress-openapi/issues/237",0.75776875,{"description":3040,"labels":3041,"number":3043,"owner":3009,"repository":3010,"state":3023,"title":3044,"updated_at":3045,"url":3046,"score":3047},"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```",[3042],{"name":3032,"color":3033},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.7693757,{"description":3049,"labels":3050,"number":3051,"owner":3009,"repository":3010,"state":3023,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### What would you like?\n\nThis is what I expect.\n\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_",[],227,"Is the application/x-www-form-urlencoded content type supported?","2025-05-29T23:41:20Z","https://github.com/enzonotario/vitepress-openapi/issues/227",0.7792125,{"description":3057,"labels":3058,"number":3060,"owner":3009,"repository":3010,"state":3023,"title":3061,"updated_at":3062,"url":3063,"score":3064},"Follow on to https://github.com/enzonotario/vitepress-theme-openapi/issues/10\r\n\r\nIt would be great to allow trying out requests that have a body required.\r\n\r\nProbably a first version of this would just provide a single text input box for the whole \"body\" to be provided.\r\n\r\nUsers could then easily copy and paste the example (probably json) body, and modify it",[3059],{"name":3032,"color":3033},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.787037,{"description":3066,"labels":3067,"number":3069,"owner":3009,"repository":3010,"state":3023,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### Current behavior\r\n\r\nMy openapi spec contains oneOf and prefixItems \r\n\r\n- [x] #124\r\n\r\n- [x] #125\r\n\r\n### Desired behavior\r\n\r\n_No response_\r\n\r\n### Reproduction\r\n\r\n_No response_\r\n\r\n### Steps to reproduce\r\n\r\n```\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:dev\r\n# for oneOf, see http://localhost:5173/api-all-in-one/#get-api-paymentAccountBroadcaster\r\n# it shows null, while null is only one of the possible type\r\n\r\n# for prefixItems I had an earlier example here : https://github.com/wighawag/fuzd/commit/d47b3452280a13aeb6d38c6c7301e51b8be7f2fc\r\n# where error (click 500) where not showing properly because I was using prefixItems\r\n```\r\n\r\n### Logs and Error Messages\r\n\r\n_No response_\r\n\r\n### Other Information\r\n\r\n_No response_",[3068],{"name":3032,"color":3033},111,"prefixItems and oneOf does not seems to be supported","2025-05-03T22:18:47Z","https://github.com/enzonotario/vitepress-openapi/issues/111",0.7966611,{"description":3075,"labels":3076,"number":1226,"owner":3009,"repository":3077,"state":3023,"title":3078,"updated_at":3079,"url":3080,"score":3081},"Hi @enzonotario \r\n\r\nFirst of all, thank you for this repo! It is very helpful.\r\nI followed exactly the steps you wrote, but i get a strange error, and i ran out of ideas what could be wrong. I receive an error message from Pusher in the console saying: json returned from auth endpoint was invalid, yet status code was 200.\r\nIn the DevTools i see that it hits the authEndpoint with status code 200, but as a response i get back the content of my app.blade.php. It is really strange. Do you have any idea what could cause this?\r\n\r\nIt's not just my app. I downloaded and installed this repo of yours, and i get the same error.",[],"lighthouse-laravel-websockets","json returned from auth endpoint was invalid, yet status code was 200.","2020-04-16T18:51:33Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/6",0.7971392,{"description":3083,"labels":3084,"number":3085,"owner":3009,"repository":3010,"state":3023,"title":3086,"updated_at":3087,"url":3088,"score":3089},"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.80771357,{"description":3091,"labels":3092,"number":1598,"owner":3009,"repository":3096,"state":3023,"title":3097,"updated_at":3098,"url":3099,"score":3100},"",[3093],{"name":3094,"color":3095},"documentation","0075ca","esjs-dolar-api","Add Dollar Blue for Bolivia","2025-02-17T22:04:29Z","https://github.com/enzonotario/esjs-dolar-api/issues/37",0.81205237,["Reactive",3102],{},["Set"],["ShallowReactive",3105],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fCCiAU_nD-MBAzUY6qEpoAK8p38bxwcKHwaSW0OV0CRo":-1},"/enzonotario/vitepress-openapi/246"]