Charts of type 'Map' broken: 'Whoops something went wrong on our side'
Hey,
we wanted to investigate on how we could get our own custom map files working with our dataflows. We have the latest Yay release deployed on our cluster, but whenever we now try to access a Chart of type 'Map' it ends up on the 'Whoops something went wrong on our side' error page. This also seems to be the case on the demo environment (i.e. https://de-demo.siscc.org/vis?fs[0]=Topic%2C0%7CEconomy%23ECO%23&fs[1]=Reference%20area%2C0%7CEuro%20area%20%2819%20countries%29%23EA19%23&pg=0&fc=Reference%20area&snb=1&vw=cp&df[ds]=ds%3Astaging%3ASIS-CC-stable&df[id]=DSD_BOP%40DF_IIP&df[ag]=OECD.SDD.TPS&df[vs]=1.0&pd=2022-Q1%2C&dq=EA19.....Q.XDC.&ly[rw]=MEASURE%2CFS_ENTRY&ly[cl]=TIME_PERIOD%2CACCOUNTING_ENTRY&to[TIME_PERIOD]=false&mp[id]=world&mp[names][en]=world%20countries&mp[names][fr]=pays%20du%20monde&mp[lv]=countries)
Some javascript error seems to be the cause:
react-dom.profiling.min.js:4068 TypeError: Cannot read properties of null (reading 'isNonCoded') at dimension-utils.js:29:24 at choro-series.js:69:16 at e.exports (_arrayMap.js:15:21) at e.exports (map.js:49:47) at t.default (choro-series.js:63:37) at index.js:431:28 at configure-map.js:56:94 at Object.<anonymous> (index.js:453:14) at Object.series (configure-map.js:56:94) at chart.js:68:18 ...
Have you also encountered this?