\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)",[3044],{"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.80817544,{"description":3051,"labels":3052,"number":3054,"owner":3023,"repository":3024,"state":3025,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### What would you like?\r\n\r\nParameter example values along with the description\r\n\r\nSo for example after I overloaded your template for this section I see this:\r\n\r\n**$filter** string\r\nExample name eq 'hello'\r\n\r\n\r\nYou can see the example [live here](https://apidev.digilean.tools/docs/operations/Boards_List) as well\r\n\r\n### Why is this needed?\r\n\r\nI see you use the example values in the playground/try it section\r\n\r\nBut I choose not to display this.\r\n\r\n### How could it be implemented?\r\n\r\nSomething like \r\n```vue\r\n\u003Cdiv v-if=\"props.parameter.example\" class=\"flex flex-row space-x-2\">\r\n \u003Cspan class=\"text-sm example font-bold\">\r\n Example\r\n \u003C/span>\r\n \u003Cspan class=\"text-sm text-gray-600 dark:text-gray-300\">\r\n {{ props.parameter.example }}\r\n \u003C/span>\r\n\u003C/div>\r\n```\r\n\r\n### Other information\r\n\r\n_No response_",[3053],{"name":3020,"color":3021},93,"Display example values for Parameters","2024-10-17T08:22:46Z","https://github.com/enzonotario/vitepress-openapi/issues/93",0.83171886,{"description":3060,"labels":3061,"number":3068,"owner":3023,"repository":3024,"state":3025,"title":3069,"updated_at":3070,"url":3071,"score":3072},"On my site I have the following in my vitepress config\r\n\r\n```\r\n search: {\r\n provider: 'local'\r\n }\r\n```\r\n\r\nper https://vitepress.dev/reference/default-theme-search\r\n\r\nHowever, pages rendered via the method suggested `*.paths.js` doesnt appear in the search.\r\n\r\n\r\n\r\nSeemingly none of the example sites currently include search, and thus the component doesnt appear to work with search?",[3062,3065],{"name":3063,"color":3064},"documentation","0075ca",{"name":3066,"color":3067},"question","d876e3",47,"Working example with search provider local set","2024-09-18T12:40:44Z","https://github.com/enzonotario/vitepress-openapi/issues/47",0.8349283,{"description":3074,"labels":3075,"number":3076,"owner":3023,"repository":3024,"state":3025,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### What would you like?\r\n\r\nFirst of all, thank you for providing this great library!\r\n\r\nIt would be great to show operation parameter descriptions, e.g. \r\n\r\n> _**GetBooks**_\r\n> \r\n> _Parameters_\r\n> **pageIndex**: The number of the page to request. The page starts with the value 0\r\n> **sort**: The field to sort the results by. Prefix by \"-\" to invert the sort.\r\n\r\n### Why is this needed?\r\n\r\nJust the name might not be sufficient for users to understand how to use a certain field. OpenAPI provides the description field for further context.\r\n\r\n### How could it be implemented?\r\n\r\nSince the parameter name, required status, and example are already shown in the \"try-it\" section, it would make sense to show the description there as well.\r\n\r\nAlternatively, parameters could be listed in a section above the response documentation.\r\n\r\n### Other information\r\n\r\nI'd be happy to help with the implementation!",[],102,"Show description field of operation parameters","2024-10-30T19:52:59Z","https://github.com/enzonotario/vitepress-openapi/issues/102",0.84006953,{"description":3082,"labels":3083,"number":1220,"owner":3023,"repository":3024,"state":3025,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Current behavior\n\nin a setup where all operations are sown in one page, the table of content contains links to each one of them as anchor links\r\n\r\nThe operation that have parameters in their url (using`{}`) have their links not working\n\n### Desired behavior\n\nI expect all links to work\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\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# click on links\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3084],{"name":3034,"color":3035},"anchor links that have parameter do not work","2024-11-06T00:17:01Z","https://github.com/enzonotario/vitepress-openapi/issues/108",0.84127975,{"description":3090,"labels":3091,"number":3093,"owner":3023,"repository":3094,"state":3025,"title":3095,"updated_at":3096,"url":3097,"score":3098},"```\r\n{\r\n\t\"moneda\": \"USD\",\r\n\t\"casa\": \"bolsa\",\r\n\t\"nombre\": \"Bolsa\",\r\n\t\"compra\": 128350,\r\n\t\"venta\": 128940,\r\n\t\"fechaActualizacion\": \"2024-09-03T12:57:00.000Z\"\r\n}\r\n```\r\n\r\nLuego de varios intentos de request por distintos medios, recibo la respuesta de los valores sin decimales tal como se ve en el ejemplo.\r\n\r\nLa respuesta que ofrece la API es correcta y debo dividir por 100 para obtener los decimales o es un bug a corregir?",[3092],{"name":3034,"color":3035},28,"esjs-dolar-api","Dolar bolsa valores sin decimales ","2024-09-03T14:53:10Z","https://github.com/enzonotario/esjs-dolar-api/issues/28",0.84755623,{"description":3100,"labels":3101,"number":3103,"owner":3023,"repository":3024,"state":3025,"title":3104,"updated_at":3105,"url":3106,"score":3107},"openapi spec allows flagging deprecated routes, such as\r\n\r\n```\r\n/pet/findByTags:\r\n get:\r\n deprecated: true\r\n```\r\n\r\nThis should be rendered in some way in the resulting component.\r\n\r\n",[3102],{"name":3020,"color":3021},43,"Support deprecated routes","2024-09-18T12:40:15Z","https://github.com/enzonotario/vitepress-openapi/issues/43",0.8475711,{"description":3109,"labels":3110,"number":3112,"owner":3023,"repository":3024,"state":3025,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### 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_",[3111],{"name":3020,"color":3021},91,"Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.84765595,["Reactive",3118],{},["Set"],["ShallowReactive",3121],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRpxB_KWMIW6owD7-0_ECFlzfOfIb-PpB7FRI2nOlWX0":-1},"/enzonotario/esjs-dolar-api/36"]