",[],288,"Support rendering model-with-annotated-enumeration in Request Body schema","2025-07-30T10:58:09Z","https://github.com/enzonotario/vitepress-openapi/issues/288",0.87076515,{"description":3036,"labels":3037,"number":2027,"owner":3020,"repository":3038,"state":3039,"title":3040,"updated_at":3041,"url":3042,"score":3043},"Hola, el valor del riesgo país último como el histórico tiene días con valores incorrectos",[],"esjs-argentina-datos-api","closed","Riesgo país inválido","2025-01-01T22:39:31Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/9",0.7722336,{"description":3045,"labels":3046,"number":3053,"owner":3020,"repository":3021,"state":3039,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### What would you like?\n\nRight now It generate such page \r\n\r\n\r\nwould like to remove Default on the side and move the table of content to the left\r\n\r\nOr alternatively, if I could change the name and add a description so the left do not feel emptu\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_",[3047,3050],{"name":3048,"color":3049},"enhancement","a2eeef",{"name":3051,"color":3052},"question","d876e3",109,"Any way to remove default or change the name and add description","2024-11-03T03:36:50Z","https://github.com/enzonotario/vitepress-openapi/issues/109",0.80106354,{"description":3059,"labels":3060,"number":104,"owner":3020,"repository":3038,"state":3039,"title":3064,"updated_at":3065,"url":3066,"score":3067},"El api esta devolviendo tna null cuando en la pagina es 73,5\r\n\r\n {\r\n \"entidad\": \"BANCO COMAFI SOCIEDAD ANONIMA\",\r\n \"logo\": \"https://www.bcra.gob.ar/Imagenes/logosbancos1/00299.jpg\",\r\n \"tnaClientes\": null,\r\n \"tnaNoClientes\": null,\r\n \"enlace\": \"https://plazofijodigital.comafi.com.ar/#/simulator/form\"\r\n },",[3061],{"name":3062,"color":3063},"bug","d73a4a","Error en tasa banco comafi","2024-03-12T15:50:38Z","https://github.com/enzonotario/esjs-argentina-datos-api/issues/3",0.81195974,{"description":3069,"labels":3070,"number":1225,"owner":3020,"repository":3071,"state":3039,"title":3072,"updated_at":3073,"url":3074,"score":3075},"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.8412029,{"description":3077,"labels":3078,"number":3080,"owner":3020,"repository":3021,"state":3039,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### Current behavior\n\nWhen calling the `getParsedSpec()` method of an `useOpenapi` instance, I get the following error:\r\n\r\n```\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'get')\r\n at P8e (vitepress-openapi.es.js:68526:53)\r\n at r (vitepress-openapi.es.js:68540:18)\r\n at r (vitepress-openapi.es.js:68542:18)\r\n at r (vitepress-openapi.es.js:68537:18)\r\n at r (vitepress-openapi.es.js:68542:18)\r\n at r (vitepress-openapi.es.js:68542:18)\r\n at r (vitepress-openapi.es.js:68542:18)\r\n at r (vitepress-openapi.es.js:68542:18)\r\n at I8e (vitepress-openapi.es.js:68546:10)\r\n at Object.i [as getParsedSpec] (vitepress-openapi.es.js:68894:22)\r\n```\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nThe open api json can be found here: https://api-docs.tacticaldefense.software/openapi.json\r\n\r\nMinimal code to reproduce:\r\n\r\n```\r\nimport { theme, useOpenapi } from 'vitepress-openapi'\r\nimport spec from 'openapi.json' assert { type: 'json' }\r\n\r\nconst openapi = useOpenapi({ spec })\r\nopenapi.getParsedSpec();\r\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\nI noticed that `@trojs/openapi-dereference` is currently on v0.2.4, but your packages.json file includes 0.2.3... maybe as easy as upgrading the version?",[3079],{"name":3062,"color":3063},78,"Cannot read properties of null (reading 'get')","2024-10-10T00:51:16Z","https://github.com/enzonotario/vitepress-openapi/issues/78",0.8465954,{"description":3086,"labels":3087,"number":3088,"owner":3020,"repository":3021,"state":3039,"title":3089,"updated_at":3090,"url":3091,"score":3092},"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.85087395,{"description":3094,"labels":3095,"number":104,"owner":3020,"repository":3097,"state":3039,"title":3098,"updated_at":3099,"url":3100,"score":3101},"Sugiero que la API retorne cotizaciones del día anterior, de esa manera se puede calcular fácilmente las variaciones porcentuales.\r\n\r\nEjemplo:\r\n\r\n```\r\n[\r\n \"Hoy\": {\r\n \"compra\": \"number\",\r\n \"venta\": \"number\",\r\n \"casa\": \"string\",\r\n \"nombre\": \"string\",\r\n \"moneda\": \"string\",\r\n \"fechaActualizacion\": \"string\"\r\n },\r\n \"Ayer\": {\r\n \"compra\": \"number\",\r\n \"venta\": \"number\",\r\n \"casa\": \"string\",\r\n \"nombre\": \"string\",\r\n \"moneda\": \"string\",\r\n \"fechaActualizacion\": \"string\"\r\n }\r\n]\r\n```",[3096],{"name":3048,"color":3049},"esjs-dolar-api","[New Feature] Añadir cotización del día anterior","2024-01-31T23:06:14Z","https://github.com/enzonotario/esjs-dolar-api/issues/3",0.8508791,{"description":3103,"labels":3104,"number":104,"owner":3020,"repository":3021,"state":3039,"title":3105,"updated_at":3106,"url":3107,"score":3101},"> operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API.\r\n\r\nAs a result my spec doesnt actually have `operationId` in it for each route\r\nIt would be great if route and method could be used in combination insead of operationId :)",[],"Allow selection by path / key as well as / insead of operationId ?","2024-08-27T23:04:25Z","https://github.com/enzonotario/vitepress-openapi/issues/3",["Reactive",3109],{},["Set"],["ShallowReactive",3112],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fr0znjCEZhDNqKcbIubI_zEZzkejUX61LLZtx2hhu7aE":-1},"/enzonotario/esjs-argentina-datos-api/8"]