Line graph dashed line not working

[CharlieTap]

Attempting to make a line graph with a simple dashed line and its not quite working, oddly it works just fine when using chart.js directly.

{
   "type":"line",
   "data":{
      "labels":[
         "July 19",
         "August 19",
         "Sept 19"
      ],
      "datasets":[
         {
            "data":[
               1.2,
               1.4
            ],
            "label":"Progress",
            "borderColor":"#1c60ab",
            "borderDash":[
               5,
               5
            ],
            "pointBackgroundColor":"#1c60ab"
         },
         {
            "data":[
               1.2,
               1.5,
               1.8
            ],
            "label":"Target",
            "borderColor":"#d7d8da",
            "borderDash":[
               5,
               5
            ],
            "pointBackgroundColor":"#d7d8da",
            "pointRadius":0
         }
      ]
   },
   "options":{
      "plugins":{
         "datalabels":{
            "display":false
         }
      },
      "scales":{
         "yAxes":[
            {
               "ticks":{
                  "beginAtZero":false
               }
            }
         ]
      },
      "elements":{
         "line":{
            "fill":false
         }
      }
   }
}

[typpo]

Hi @CharlieTap,

This one took me a while to figure out. It's caused by this bug in the vm2 package, which is how we run sandboxed code for each chart: patriksimek/vm2#198

I put in a workaround that fixes the malformed array object that is produced, so things look good now:

Your browser may have cached the bad (non-dashed) images. If images you've loaded in the past are still rendering incorrectly you can clear your cache, change you config object slightly, or add a cache-busting param (e.g. q=<timestamp>) to your request in order to see the corrected graphs.

I'll keep this issue open until vm2 has fixed the problem and I can remove the workaround.

[CharlieTap]

Perfect thank you

[typpo]

Closing this now as the workaround is documented in code. Thanks for the report :)