\n\nWhich looks nice, and is copyable in the left-hand side, however the right hand side syas [object Obvject] etc...\n\n---------------\n\nWhen specifying strings of json as the filters like this\n\n```\n 'filter': [\n '{\"limit\":10,\"order\":[\"timestamp DESC\"]}',\n '{\"where\":{\"timestamp\":{\"between\":[\"2024-12-01T00:00:00.000Z\",\"2024-12-01T23:59:59.999Z\"]}},\"order\":[\"timestamp DESC\"]}',\n '{\"where\":{\"correlationId\":\"abc123\"}}',\n ],\n```\n\nWe get an ugly left-hand side with escaping, and a nice right-hand side placeholder (no extra escaping)\n\n\u003Cimg width=\"1509\" height=\"220\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a411efc1-f555-4d69-abb3-0dab9ee25450\" />\n\nUltimately in one of these cases, I would like the left-hand side to have a copyable string without escaping of \", and in the right-hand side it still be shown nicely in the placeholder.",[],301,"Consistently handle example json escaping","2025-08-28T15:58:55Z","https://github.com/enzonotario/vitepress-openapi/issues/301",0.8544095,{"description":3188,"labels":3189,"number":2053,"owner":3172,"repository":3190,"state":3191,"title":3192,"updated_at":3193,"url":3194,"score":3195},"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":3197,"labels":3198,"number":3205,"owner":3172,"repository":3173,"state":3191,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### 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_",[3199,3202],{"name":3200,"color":3201},"enhancement","a2eeef",{"name":3203,"color":3204},"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":3211,"labels":3212,"number":104,"owner":3172,"repository":3190,"state":3191,"title":3216,"updated_at":3217,"url":3218,"score":3219},"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 },",[3213],{"name":3214,"color":3215},"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":3221,"labels":3222,"number":3224,"owner":3172,"repository":3173,"state":3191,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### 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?",[3223],{"name":3214,"color":3215},78,"Cannot read properties of null (reading 'get')","2024-10-10T00:51:16Z","https://github.com/enzonotario/vitepress-openapi/issues/78",0.8465954,{"description":3230,"labels":3231,"number":3232,"owner":3172,"repository":3173,"state":3191,"title":3233,"updated_at":3234,"url":3235,"score":3236},"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":3238,"labels":3239,"number":104,"owner":3172,"repository":3241,"state":3191,"title":3242,"updated_at":3243,"url":3244,"score":3245},"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```",[3240],{"name":3200,"color":3201},"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":3247,"labels":3248,"number":104,"owner":3172,"repository":3173,"state":3191,"title":3249,"updated_at":3250,"url":3251,"score":3245},"> 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",{"description":3253,"labels":3254,"number":3255,"owner":3172,"repository":3173,"state":3191,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### 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.85114235,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fr0znjCEZhDNqKcbIubI_zEZzkejUX61LLZtx2hhu7aE":-1},"/enzonotario/esjs-argentina-datos-api/8"]