Network clustering: Cannot read property 'font' of undefined

[AoDev]

Hi, I have basically copied the example of clustering here.

Just using my own data.

when initiating the graph

var container = document.getElementById('#network')
this.graph = new vis.Network(container, {}, graphOptions)

When getting the data (before, I add a group property to each node)

    this.graph.setData(graphData)

    var groups = ['group1', 'group2', 'group3']
    var clusterOptionsByData
    for (var i = 0; i < groups.length; i++) {
      var group = groups[i]
      clusterOptionsByData = {
        joinCondition (childOptions) {
          return childOptions.group === group
        },
        clusterNodeProperties: {
          id: 'cluster:' + group,
          borderWidth: 3,
          shape: 'dot',
          color: '#000',
          label: 'group:' + group,
          font: {
            color: '#000',
            size: 14
          }
        }
      }

      this.graph.cluster(clusterOptionsByData)
    }

My graph config

const graphOptions = {
  physics: false,
  edges: {
    arrows: 'to',
    physics: false,
    scaling: {
      min: 1,
      max: 5,
      label: {
        enabled: false
      }
    },
    smooth: {
      enabled: false,
      type: 'cubicBezier',
      forceDirection: 'vertical',
      roundness: 0.5
    }
  },
  nodes: {
    shape: 'dot',
    scaling: {
      min: 10,
      max: 30,
      label: {
        enabled: false
      }
    },
    font: {
      strokeWidth: 2,
      strokeColor: '#fff',
      multi: 'html'
    }
  },
  layout: {
    improvedLayout: true,
    hierarchical: {
      enabled: true,
      levelSeparation: 150,
      nodeSpacing: 200,
      treeSpacing: 200,
      blockShifting: true,
      edgeMinimization: true,
      parentCentralization: true,
      direction: 'UD',        // UD, DU, LR, RL
      sortMethod: 'directed'   // hubsize, directed
    }
  }
}

Stacktrace:

TypeError: Cannot read property 'font' of undefined
    at Label.propagateFonts (vis.js:34775)
    at Cluster.setOptions (vis.js:34226)
    at Cluster.Node (vis.js:34126)
    at new Cluster (vis.js:43598)
    at NodesHandler.create (vis.js:33809)
    at ClusterEngine._cluster (vis.js:42959)
    at ClusterEngine.cluster (vis.js:42556)
    at Network.cluster (vis.js:33010)

I believe it breaks in Label, here
because for some reason options was not passed / is undefined.

[mojoaxel]

@AoDev Thanks for the details problem description. But I can not reproduce this problem with your example-code: http://jsbin.com/foyufig/1/edit?html,js,console,output

Can you please try to reproduce the error in a public jsbin. Thanks.

[AoDev]

Thanks, I'll try tomorrow.

What I can say is, by removing the nodes.font.multi from my config, which is currently set to html, then it will render the cluster properly. Mainly because this propagateFonts seems to run only when the multi option is set.

[Tooa]

Please provide us a minimal example via jsbin.com showing the error and explain how to reproduce the issue.

[AoDev]

@Tooa http://jsbin.com/vorozibulo/edit?html,js,console,output @mojoaxel jsbin was missing the grouping.

[arunkumarpro1]

@wimrijnders I am still getting this error. Is there any fix for this?

[wimrijnders]

@arunkumarpro1 I just scanned the issues; I am under the impression that this was fixed with #3025 and released in vis v1.20.0. Are you using this version or later?

If not, please upgrade first. Otherwise, the workaround is setting option options.nodes.font.multi: false.

Please notify me about the vis-version used, and if given workaround works. If this does not solve it, I may need to look at this issue in-depth.

[arunkumarpro1]

@wimrijnders I am using vis v4.20.1.

Yes the given workaround works fine for me. I can set options.nodes.font.multi to false for now.
Thanks a lot 👍

[wimrijnders]

OK good. However, it worries me that this still occurs. Will dive into this issue regardless.

[arunkumarpro1]

Yes. That would be really great.

[arunkumarpro1]

Yes, I have. The given workaround is fine for me.

[wimrijnders]

@arunkumarpro1 There is a fix for this issue. Will hopefully be in the next release.