\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",[3182,3185],{"name":3183,"color":3184},"enhancement","a2eeef",{"name":3186,"color":3187},"help wanted","008672",171,"Performance issues","2025-02-08T02:57:38Z","https://github.com/enzonotario/vitepress-openapi/issues/171",0.8317788,{"description":3194,"labels":3195,"number":3196,"owner":3172,"repository":3173,"state":3197,"title":3198,"updated_at":3199,"url":3200,"score":3201},"Tried on 0.0.3-alpha.63, and 0.0.3-alpha.79 (latest release)\n\nI have a header such as this defined\n\n```\n {\n \"description\": \"Optionally provide parameters as a JSON object in this header. If both query params and X-Query overlap, a 400 error is returned.\",\n \"example\": \"{\\\"id\\\":\\\"1\\\"}\",\n \"in\": \"header\",\n \"name\": \"X-Query\",\n \"schema\": {\n \"type\": \"string\"\n }\n }\n```\n\nBut also a param like this\n\n```\n {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"in\": \"query\",\n \"name\": \"id\",\n \"schema\": {\n \"description\": \"Filter by ID (comma separated for multiple values)\",\n \"example\": \"1\",\n \"form\": \"id\",\n \"type\": \"string\"\n }\n },\n```\n\nBoth of these examples are used by the UI component, and provided in the default try it requests.\nHowever this means that the request will always fail, as the examples conflict with each other.\nHowever, I want to be able to provide real examples to both of these...\n\nI think that either\n1) Examples should not be used in the default try it param\n2) There should be an option to disable it?",[],221,"closed","example should not always be used as the default for the UI","2025-05-18T01:43:41Z","https://github.com/enzonotario/vitepress-openapi/issues/221",0.74164504,{"description":3203,"labels":3204,"number":3205,"owner":3172,"repository":3173,"state":3197,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### 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.78295714,{"description":3211,"labels":3212,"number":3214,"owner":3172,"repository":3173,"state":3197,"title":3215,"updated_at":3216,"url":3217,"score":3218},"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```",[3213],{"name":3183,"color":3184},223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.8011443,{"description":3220,"labels":3221,"number":3222,"owner":3172,"repository":3173,"state":3197,"title":3223,"updated_at":3224,"url":3225,"score":3226},"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.80227995,{"description":3228,"labels":3229,"number":3230,"owner":3172,"repository":3173,"state":3197,"title":3231,"updated_at":3232,"url":3233,"score":3234},"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.8093299,{"description":3236,"labels":3237,"number":3241,"owner":3172,"repository":3173,"state":3197,"title":3242,"updated_at":3243,"url":3244,"score":3245},"### 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_",[3238],{"name":3239,"color":3240},"bug","d73a4a",236,"Long Authorization example doesnt display nicely","2025-06-22T12:55:43Z","https://github.com/enzonotario/vitepress-openapi/issues/236",0.8128635,{"description":3247,"labels":3248,"number":3250,"owner":3172,"repository":3173,"state":3197,"title":3251,"updated_at":3252,"url":3253,"score":3254},"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",[3249],{"name":3183,"color":3184},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.8143132,{"description":3256,"labels":3257,"number":1672,"owner":3172,"repository":3258,"state":3197,"title":3259,"updated_at":3260,"url":3261,"score":3262},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],"esjs-dolar-api","H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.8180401,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUYPB8nwTjBhSYUlyGH7NUty4dL81K3G8Jyn1zral-xk":-1},"/enzonotario/vitepress-openapi/301"]