\n\n### Desired behavior\n\nA performance score of 90 or above\n\n### Reproduction\n\nhttps://vitepress-openapi.vercel.app/example/operations/getAllArtists.html\n\n### Steps to reproduce\n\n- Open any page generated by this plugin\n- Open Lighthouse\n- Look at the performance score\n",[3171,3174],{"name":3172,"color":3173},"enhancement","a2eeef",{"name":3175,"color":3176},"help wanted","008672",171,"enzonotario","vitepress-openapi","open","Performance issues","2025-02-08T02:57:38Z","https://github.com/enzonotario/vitepress-openapi/issues/171",0.7925658,{"description":3186,"labels":3187,"number":1511,"owner":3178,"repository":3179,"state":3189,"title":3190,"updated_at":3191,"url":3192,"score":3193},"### What would you like?\r\n\r\nCurrently, each endpoint can only use 1 securityScheme despite OAS 3 being able to specify multiple securityScheme must be used together \r\nhttps://swagger.io/docs/specification/v3_0/authentication/#using-multiple-authentication-types\r\n\r\nDefining security schemes:\r\n```json\r\n\"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"type\": \"http\",\r\n \"scheme\": \"bearer\",\r\n \"description\": \"API Key\"\r\n },\r\n \"Signature\": {\r\n \"name\": \"x-signature\",\r\n \"type\": \"apiKey\",\r\n \"in\": \"header\",\r\n \"description\": \"Request signature\"\r\n }\r\n },\r\n```\r\n\r\nIn endpoint:\r\n```json\r\n\"security\": [{ \"Signature\": [] }, { \"ApiKeyAuth\": [] }],\r\n```\r\n\r\n### Why is this needed?\r\n\r\nWhen allowing user to test the endpoints, if the API requires 2+ security schemes to be used together, the try it would not able to show 2 security fields\r\n\r\n\r\n\r\n### How could it be implemented?\r\n\r\nUpdating OASecurity and OATryWithVariables\r\n\r\n### Other information\r\n\r\nExample implementation from [Scalar](https://github.com/scalar/scalar):\r\n\r\n",[3188],{"name":3172,"color":3173},"closed","Support multiple security together when specified","2024-12-21T01:50:26Z","https://github.com/enzonotario/vitepress-openapi/issues/129",0.72850865,{"description":3195,"labels":3196,"number":352,"owner":3178,"repository":3179,"state":3189,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### Current behavior\n\nWhen showing operations by path, the full path name is not shown for sub-paths of the operation. This can slightly be worked around by flattening to a depth of 2, but this does not work if there are no other paths after.\n\nFor example, if you have the paths /artists and /artists/{id} it will just show /artists and then /{id} as the sub-path below it.\n\nYou can see this in the stackblitz example here: [stackblitz example](https://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-cqsbxmar?file=public%2Fopenapi.json) (forked from an example you provided another user)\n\nIf you look, you'll notice that the globalv2/attachments/{id} has the issue even when flattening. You can see the same behavior for /artists in the example if you remove the /user/signup endpoint from openapi.json. For some reason, the existence of another endpoint after the /{id} does allow it to show the full path for those /{id} endpoints.\n\n\n\n\n\n### Desired behavior\n\nThe desired behavior would be to have the full path shown for sub-paths and not just show /{id}, even when there are no other sub-paths to the group of items.\n\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-cqsbxmar?file=public%2Fopenapi.json\n\n### Steps to reproduce\n\nOpen the sidebar and view the paths documented. Without flattening, the sub-path will always just show /{id}. If you flatten to a depth of 2, it will resolve the issue unless there are no other endpoints after the /{id} sub-path.\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[],"Issue showing full path name when showing operations by path","2025-01-29T14:29:13Z","https://github.com/enzonotario/vitepress-openapi/issues/163",0.75698733,{"description":3202,"labels":3203,"number":3205,"owner":3178,"repository":3179,"state":3189,"title":3206,"updated_at":3207,"url":3208,"score":3209},"Seria interesante que haya una documentación que logre adaptarse al lenguaje seleccionado desde un selector. Ya dependería de uno agregar algún lenguaje adicional en nuestra docs del proyecto. ",[3204],{"name":3172,"color":3173},128,"Multilenguaje ","2024-12-15T03:19:43Z","https://github.com/enzonotario/vitepress-openapi/issues/128",0.7785839,{"description":3211,"labels":3212,"number":1612,"owner":3178,"repository":3216,"state":3189,"title":3217,"updated_at":3218,"url":3219,"score":3220},"",[3213],{"name":3214,"color":3215},"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.78309035,{"description":3222,"labels":3223,"number":3228,"owner":3178,"repository":3179,"state":3189,"title":3229,"updated_at":3230,"url":3231,"score":3232},"On my site I have the following in my vitepress config\r\n\r\n```\r\n search: {\r\n provider: 'local'\r\n }\r\n```\r\n\r\nper https://vitepress.dev/reference/default-theme-search\r\n\r\nHowever, pages rendered via the method suggested `*.paths.js` doesnt appear in the search.\r\n\r\n\r\n\r\nSeemingly none of the example sites currently include search, and thus the component doesnt appear to work with search?",[3224,3225],{"name":3214,"color":3215},{"name":3226,"color":3227},"question","d876e3",47,"Working example with search provider local set","2024-09-18T12:40:44Z","https://github.com/enzonotario/vitepress-openapi/issues/47",0.7854001,{"description":3234,"labels":3235,"number":3236,"owner":3178,"repository":3179,"state":3189,"title":3237,"updated_at":3238,"url":3239,"score":3240},"Hi! I was working on my current project, where I have a schema that produces this UI:\n\nhttps://github.com/user-attachments/assets/21f90ff1-fb58-4aff-86e5-249e453c829f\n\nThis little screencast aims to show that it's a bit non-obvious - especially for people who are just starting to explore the site with the spec and don't know how the UI works - that object properties are there. Long description with some markdown/emojis makes it seem like the description is all that exists under this property.\n\nIn contrast, when there's no description, it's pretty obvious that the properties are expandable:\n\n\u003Cimg width=\"390\" height=\"113\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5b945a5a-e471-44b3-8f18-0e0219c8caa0\" />\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.7857505,{"description":3242,"labels":3243,"number":3245,"owner":3178,"repository":3179,"state":3189,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### 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!",[3244],{"name":3172,"color":3173},141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.78933483,{"description":3251,"labels":3252,"number":1672,"owner":3178,"repository":3216,"state":3189,"title":3253,"updated_at":3254,"url":3255,"score":3256},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],"H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.7909857,{"description":3258,"labels":3259,"number":3261,"owner":3178,"repository":3179,"state":3189,"title":3262,"updated_at":3263,"url":3264,"score":3265},"### What would you like?\n\nWhen operations with different tags are rendered on the same page, they should be grouped by tags, as it happens in Swagger.\r\n\r\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_",[3260],{"name":3172,"color":3173},81,"Group operations into tags groups","2024-10-12T13:41:02Z","https://github.com/enzonotario/vitepress-openapi/issues/81",0.79543525,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgRHH5iLJGhoqNj8tO8_FaA_qP4xtEw498LL9mPMhHCw":-1},"/enzonotario/vitepress-openapi/91"]