\r\n```\n\n### Logs and Error Messages\n\n\u003C--- Last few GCs --->\r\n\r\n[8528:0000028921749270] 51958 ms: Scavenge 4038.9 (4137.2) -> 4038.5 (4142.0) MB, 5.89 / 0.00 ms (average mu = 0.723, current mu = 0.560) allocation failure;\r\n[8528:0000028921749270] 53307 ms: Mark-Compact 4042.1 (4142.2) -> 4040.3 (4145.0) MB, 1345.40 / 0.00 ms (average mu = 0.530, current mu = 0.017) allocation failure; scavenge might not succeed\r\n\r\n\r\n\u003C--- JS stacktrace --->\r\n\r\nFATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory\r\n----- Native stack trace -----\r\n\r\n 1: 00007FF7257A39EB node::SetCppgcReference+18459\r\n 2: 00007FF725713238 DSA_meth_get_flags+93160\r\n 3: 00007FF72618C771 v8::Isolate::ReportExternalAllocationLimitReached+65\r\n 4: 00007FF726175EC8 v8::Function::Experimental_IsNopFunction+1336\r\n 5: 00007FF725FD7970 v8::Platform::SystemClockTimeMillis+659328\r\n 6: 00007FF725FD49F8 v8::Platform::SystemClockTimeMillis+647176\r\n 7: 00007FF725FE9D0A v8::Platform::SystemClockTimeMillis+733978\r\n 8: 00007FF725FEA587 v8::Platform::SystemClockTimeMillis+736151\r\n 9: 00007FF725FF8E7F v8::Platform::SystemClockTimeMillis+795791\r\n10: 00007FF725CB9565 v8::CodeEvent::GetFunctionName+116773\r\n11: 00007FF72623E0FE v8::PropertyDescriptor::writable+678094\r\n12: 00007FF6A726D238\n\n### Other Information\n\nDuring the build, I also get many errors like this:\r\n\r\nReferenceError: localStorage is not defined\r\n at file:///C:/Repos/Work/\u003Credactedname>/Docs/node_modules/vitepress-theme-openapi/dist/vitepress-theme-openapi.es.js:66959:56\r\n at Array.map (\u003Canonymous>)\r\n at setup (file:///C:/Repos/Work/\u003Credactedname>/Docs/node_modules/vitepress-theme-openapi/dist/vitepress-theme-openapi.es.js:66957:43)\r\n at callWithErrorHandling (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.cjs.prod.js:86:19)\r\n at setupStatefulComponent (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.cjs.prod.js:6241:25)\r\n at setupComponent (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.cjs.prod.js:6228:36)\r\n at renderComponentVNode (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:376:15)\r\n at renderVNode (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:507:14)\r\n at renderVNodeChildren (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:523:5)\r\n at renderElementVNode (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:567:9)\r\nReferenceError: localStorage is not defined\r\n at file:///C:/Repos/Work/\u003Credactedname>/Docs/node_modules/vitepress-theme-openapi/dist/vitepress-theme-openapi.es.js:66959:56\r\n at Array.map (\u003Canonymous>)\r\n at setup (file:///C:/Repos/Work/\u003Credactedname>/Docs/node_modules/vitepress-theme-openapi/dist/vitepress-theme-openapi.es.js:66957:43)\r\n at callWithErrorHandling (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.cjs.prod.js:86:19)\r\n at setupStatefulComponent (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.cjs.prod.js:6241:25)\r\n at setupComponent (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\runtime-core\\dist\\runtime-core.cjs.prod.js:6228:36)\r\n at renderComponentVNode (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:376:15)\r\n at renderVNode (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:507:14)\r\n at renderVNodeChildren (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:523:5)\r\n at renderElementVNode (C:\\Repos\\Work\\\u003Credactedname>\\Docs\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:567:9)",[3033],{"name":3020,"color":3021},65,"Build fails with \"heap limit allocation failed\"","2024-10-29T16:35:25Z","https://github.com/enzonotario/vitepress-openapi/issues/65",0.80693746,{"description":3040,"labels":3041,"number":3045,"owner":3023,"repository":3024,"state":3025,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### Current behavior\n\nThis is much like #11 \r\nIf you have a query parameter that is a boolean, it will not be displayed in the Variables list; see image.\r\n\r\n\r\nHowever, if I change the type to string, it works as expected.\r\n\r\nHere is the relevant snipit from the openapi file:\r\n\r\n```\r\n use_csv:\r\n name: use_csv\r\n in: query\r\n required: true\r\n schema:\r\n type: boolean\r\n default: false\r\n example: false\r\n description: 'Uses the [legacy JSON](docs/Data-And-Requests/Legacy-JSON-Responses.md) format if ``false``.'\r\n```\n\n### Desired behavior\n\nI would expect this variable to appear (checkbox maybe?), and allow me to set it.\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nJust create a OAS with a query parameter of `boolean`\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3042],{"name":3043,"color":3044},"bug","d73a4a",83,"Boolean query parameters are not displayed in variable list","2024-10-12T14:54:04Z","https://github.com/enzonotario/vitepress-openapi/issues/83",0.80764824,{"description":3051,"labels":3052,"number":3056,"owner":3023,"repository":3024,"state":3025,"title":3057,"updated_at":3058,"url":3059,"score":3060},"### What would you like?\n\nVitepress-openapi is beautiful. I have a doc site already, and I would like to add the vitepress-openapi docs as a menu item on my top navigation menu. \r\n\r\n\r\n\n\n### Why is this needed?\n\nThere is often a lot of material besides the openapi specification that one needs for documentation. I'd like to be able to include the openapi site within another site to keep everything together.\n\n### How could it be implemented?\n\nI'm not knowledgeable enough to know. Right now I am embedding `openapi-explorer` in a simple `layout: page` page associated with the menu item:\r\n\r\n```vue\r\n---\r\nlayout: page\r\nsidebar: false\r\n---\r\n\u003Cscript setup>\r\n import 'openapi-explorer/dist/es/openapi-explorer.js';\r\n import { useData } from 'vitepress'\r\n const { isDark, theme, page, frontmatter } = useData()\r\n\u003C/script>\r\n\r\n\u003CClientonly>\r\n \u003Copenapi-explorer\r\n v-if = isDark\r\n spec-url = \"/adm-spec.yaml\"\r\n hide-console = true\r\n hide-authentication = true\r\n hide-server-selection = true\r\n hide-components = false\r\n nav-bg-color = #1b1b1f\r\n secondary-color = #F8F8F5\r\n nav-hover-text-color = #85bd4f\r\n bg-color = #1b1b1f\r\n text-color = \"#F8F8F5\"\r\n >\r\n \u003C/openapi-explorer>\r\n\r\n\r\n \u003Copenapi-explorer\r\n v-else\r\n spec-url = \"/adm-spec.yaml\"\r\n hide-console = true\r\n hide-authentication = true\r\n hide-server-selection = true\r\n hide-components = false\r\n nav-bg-color = #ffffff\r\n secondary-color = #000000\r\n nav-hover-text-color = #F8F8F5\r\n >\r\n \u003C/openapi-explorer>\r\n\r\n\u003C/ClientOnly>\r\n```\r\n\r\nThis seems very awkward, and it's difficult to get the styles to match Vitepress's theme. Might there be a way to extend the default theme with a layout called `openapi` and somehow link my spec file in the front matter?\n\n### Other information\n\nI appreciate this work very much. Thanks for considering the suggestion.",[3053],{"name":3054,"color":3055},"question","d876e3",71,"Is it possible to add vitepress-openapi to an existing Vitepress site as a menu item","2024-10-19T02:30:08Z","https://github.com/enzonotario/vitepress-openapi/issues/71",0.80949,{"description":3062,"labels":3063,"number":3065,"owner":3023,"repository":3024,"state":3025,"title":3066,"updated_at":3067,"url":3068,"score":3069},"Take the following minimal crashable example:\r\n\r\n```json\r\n{\r\n \"openapi\": \"3.0.0\",\r\n \"info\": {\r\n \"title\": \"Minimal API with Circular Reference\",\r\n \"version\": \"1.0.0\"\r\n },\r\n \"paths\": {\r\n \"/parent\": {\r\n \"get\": {\r\n \"summary\": \"Get a parent\",\r\n \"operationId\": \"getParent\",\r\n \"responses\": {\r\n \"200\": {\r\n \"description\": \"A parent with a child\",\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/Parent\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"components\": {\r\n \"schemas\": {\r\n \"Parent\": {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"string\"\r\n },\r\n \"child\": {\r\n \"$ref\": \"#/components/schemas/Child\"\r\n }\r\n }\r\n },\r\n \"Child\": {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"string\"\r\n },\r\n \"parent\": {\r\n \"$ref\": \"#/components/schemas/Parent\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\nThis is valid openapi spec as can be seen checked using a [validator](https://apitools.dev/swagger-parser/online/). Of course, dealing with a circular swagger requires a form of normalization. \r\n\r\nI am currently using the standard swagger UI, which does nicely deal with circular references. However, as I have moved all my documentation over to vitepress, I would also prefer to maybe include some swagger here and there as it could help make explanations a bit clearer.",[3064],{"name":3043,"color":3044},57,"[BUG] Generator crashes if openapi-spec contains a circular reference","2024-09-28T15:43:59Z","https://github.com/enzonotario/vitepress-openapi/issues/57",0.81050575,{"description":3071,"labels":3072,"number":3075,"owner":3023,"repository":3024,"state":3025,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Current behavior\r\n\r\nI just added vitepress-openapi as documented + added the markdown file \r\n\r\nAnd I get many errors\r\nthe last one shown being:\r\n\r\n```\r\nBuild failed with 1 error:\r\nnode_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:1225:27: ERROR: [plugin: externalize-deps] \"vitepress-openapi\" resolved to an ESM file. ESM file cannot be loaded by `require`. See https://vite.dev/guide/troubleshooting.html#this-package-is-esm-only for more details.\r\nError: Build failed with 1 error:\r\nnode_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:1225:27: ERROR: [plugin: externalize-deps] \"vitepress-openapi\" resolved to an ESM file. ESM file cannot be loaded by `require`. See https://vite.dev/guide/troubleshooting.html#this-package-is-esm-only for more details.\r\n at failureErrorWithLog (/home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:1472:15)\r\n at /home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:945:25\r\n at runOnEndCallbacks (/home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:1315:45)\r\n at buildResponseToResult (/home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:943:7)\r\n at /home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:970:16\r\n at responseCallbacks.\u003Ccomputed> (/home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:622:9)\r\n at handleIncomingPacket (/home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:677:12)\r\n at Socket.readFromStdout (/home/wighawag/dev/github.com/wighawag/fuzd/node_modules/.pnpm/esbuild@0.21.5/node_modules/esbuild/lib/main.js:600:7)\r\n at Socket.emit (node:events:519:28)\r\n at addChunk (node:internal/streams/readable:561:12)\r\n⠦ building client + server bundles...\r\n```\r\n\r\n### Desired behavior\r\n\r\nNo error\r\n\r\n### Reproduction\r\n\r\n_No response_\r\n\r\n### Steps to reproduce\r\n\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:build\r\n\r\n### Logs and Error Messages\r\n\r\n_No response_\r\n\r\n### Other Information\r\n\r\n_No response_",[3073,3074],{"name":3043,"color":3044},{"name":3054,"color":3055},105,"Errors when building docs","2024-11-02T06:51:12Z","https://github.com/enzonotario/vitepress-openapi/issues/105",0.81329614,{"description":3081,"labels":3082,"number":3086,"owner":3023,"repository":3024,"state":3025,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### Current behavior\n\nI am using\r\n\r\n```\r\nuseTheme({\r\n\trequest: {\r\n\t\t// Set the default schema view.\r\n\t\tdefaultView: 'schema', // schema or contentType\r\n\t},\r\n});\r\n```\r\n\r\nto set the default view to schema but this does not work\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:dev\r\n# navigate to http://localhost:5173/api-all-in-one/\r\n# it still use JSON as default view\r\n```\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3083],{"name":3084,"color":3085},"documentation","0075ca",107,"useTheme have no effect","2024-11-02T22:51:19Z","https://github.com/enzonotario/vitepress-openapi/issues/107",0.82075673,{"description":3092,"labels":3093,"number":3095,"owner":3023,"repository":3096,"state":3025,"title":3097,"updated_at":3098,"url":3099,"score":3100},"# Agregar Aplicación a la lista de aplicaciones que consumen DolarApi.com\n\n## Información de la Aplicación\n\n- **Nombre de la Aplicación:**\n Dólar Ahora\n\n- **URL de la Aplicación:**\n https://play.google.com/store/apps/details?id=com.fraancogaalfras.dolarahora\n\n- **Descripción de la Aplicación:**\n App móvil para consultar el precio de los dólares financieros en Argentina.\n",[3094],{"name":3084,"color":3085},39,"esjs-dolar-api","Listar Aplicación - Dólar Ahora","2025-03-01T20:46:40Z","https://github.com/enzonotario/esjs-dolar-api/issues/39",0.8256203,{"description":3102,"labels":3103,"number":3104,"owner":3023,"repository":3024,"state":3025,"title":3105,"updated_at":3106,"url":3107,"score":3108},"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.8257225,{"description":3110,"labels":3111,"number":3113,"owner":3023,"repository":3024,"state":3025,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### What would you like?\n\nI'd like to be able to render the openapi specification with a signle column layout. It would be nice if it is configurable in the parameters of the components like OASpec or globally in the theme config. In addition to that, it would also be nice if the different child components could be enabled/disabled (i.e. turn off samples). \n\n### Why is this needed?\n\nI want this because the standard theme does not have a lot of content width, Having a two column layout looks crowded and sometimes the content is wrapped. Having all the child components below each other with a single column layout would bring more clarity to the rendered documentation.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3112],{"name":3020,"color":3021},91,"Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.8282594,["Reactive",3119],{},["Set"],["ShallowReactive",3122],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUzeteAZT3ou4RI9zH109ExYcPScUxtUgF42opMVoXrA":-1},"/enzonotario/vitepress-openapi/93"]