\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? :)",[3020],{"name":3021,"color":3022},"enhancement","a2eeef","enzonotario","vitepress-openapi","closed","Enable rendering components for multiple specs on a single page.","2024-09-28T15:44:23Z","https://github.com/enzonotario/vitepress-openapi/issues/21",0.7888753,{"description":3031,"labels":3032,"number":3033,"owner":3023,"repository":3024,"state":3025,"title":3034,"updated_at":3035,"url":3036,"score":3037},"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.80443627,{"description":3039,"labels":3040,"number":1598,"owner":3023,"repository":3024,"state":3025,"title":3042,"updated_at":3043,"url":3044,"score":3045},"So, hvaing this in the front matter\r\n\r\n```\r\naside: true\r\noutline: true\r\n``` \r\n\r\nout of the box results in a very verbose set of headings.\r\n\r\nIt might be nice for the default heading levels (or tags used) to present themselves a little nicer in the asied outline!\r\n\r\n\r\n",[3041],{"name":3021,"color":3022},"Allow choosing component heading levels","2024-09-19T22:35:35Z","https://github.com/enzonotario/vitepress-openapi/issues/37",0.8231001,{"description":3047,"labels":3048,"number":3052,"owner":3023,"repository":3024,"state":3025,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### What would you like?\n\nCurrently, When typing in the search box, no api get shown even if they should match the query\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_",[3049],{"name":3050,"color":3051},"question","d876e3",115,"api should appear in search","2024-11-04T00:50:21Z","https://github.com/enzonotario/vitepress-openapi/issues/115",0.83975893,{"description":3058,"labels":3059,"number":3061,"owner":3023,"repository":3024,"state":3025,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### 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_",[3060],{"name":3021,"color":3022},222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.8457722,{"description":3067,"labels":3068,"number":3069,"owner":3023,"repository":3024,"state":3025,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### 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.8464583,{"description":3075,"labels":3076,"number":285,"owner":3023,"repository":3080,"state":3025,"title":3081,"updated_at":3082,"url":3083,"score":3084},"La api esta fallando con el valor del dolar blue",[3077],{"name":3078,"color":3079},"duplicate","cfd3d7","esjs-dolar-api","Error en la cotización del blue","2024-02-09T14:55:00Z","https://github.com/enzonotario/esjs-dolar-api/issues/15",0.8502885,{"description":3086,"labels":3087,"number":3088,"owner":3023,"repository":3080,"state":3025,"title":3089,"updated_at":3090,"url":3091,"score":3092},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],40,"H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.8506338,{"description":3094,"labels":3095,"number":3097,"owner":3023,"repository":3024,"state":3025,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### What would you like?\n\nI wonder if it is possible to implement path based sidebar. For example, we have\r\n\r\n```\r\n/api/v1/products CRUD\r\n/api/v1/orders CRUD\r\n```\r\n\r\nSidebar would look like\r\n\r\n```\r\n/api/v1\r\n ├ products\r\n | ├ PUT\r\n | ├ GET\r\n | ├ POST\r\n | └ DELETE\r\n └ orders\r\n ├ PUT\r\n ├ GET\r\n ├ POST\r\n └ DELETE\r\n```\r\n\r\n**Note**: empty folders are collapsed\r\n\n\n### Why is this needed?\n\nI want to use more than one tag per endpoint. But in this case sidebar looks strange. Maybe there is a way to organize sidebar better even if there are multiple tags...\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3096],{"name":3021,"color":3022},119,"Path based sidebar","2024-12-12T03:25:21Z","https://github.com/enzonotario/vitepress-openapi/issues/119",0.8508618,{"description":3103,"labels":3104,"number":1662,"owner":3023,"repository":3105,"state":3025,"title":3106,"updated_at":3107,"url":3108,"score":3109},"https://www.bcra.gob.ar/Catalogo/apis.asp?fileName=central-deudores-v1§ionName=Central%20de%20Deudores",[],"esjs-argentina-datos-api","Sumar datos de las APIs de deudores del BCRA","2025-02-19T00:26:37Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/11",0.8521395,["Reactive",3111],{},["Set"],["ShallowReactive",3114],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDJKfPkNKf4OrMpjR-YAlm7sB60LLjbgp6Cqbmea7xGc":-1},"/enzonotario/esjs-dolar-api/17"]