v3 - arc layer blowing up about deck.gl HOT 4 CLOSED

@contra - As a first step, make sure you take note of the breaking API change in v3. In contrast to v2, deck.gl v3 expects arrays for all positions, colors etc (instead of objects {x,y,z}, {r,g,b} etc.. It also introduces accessors that can help if your data is not organized the right way.

from deck.gl.

@ibgreen Ah, wasn't aware of that. Checked the changelog and docs and didn't see any mention of that. I'll give it a try.

from deck.gl.

@ibgreen Just to clarify: The API for arcs should be like this?

position: [
  [ x, y, z ],
  [ x, y, z ]
]

from deck.gl.

@contra

Checked the changelog and docs and didn't see any mention of that

Yes I guess you would need to check the CHANGELOG on the dev branch, there is a small note: https://github.com/uber/deck.gl/blob/dev/CHANGELOG.md#300-beta13--

The API for arcs should be like this?

Per default accessors they should be called sourcePosition and targetPosition.
But by supplying custom accessors you could store them anyway you want.

https://github.com/uber/deck.gl/blob/dev/src/layers/core/arc-layer/arc-layer.js#L118
https://github.com/uber/deck.gl/blob/dev/src/layers/core/arc-layer/arc-layer.js#L27

from deck.gl.