Closed jadh4v closed 1 year ago
Oh, I didn't realize you were looking into this from the react-vtk-js side. This was fixed in vtk.js proper: https://github.com/Kitware/vtk-js/pull/2872
LGTM!
:tada: This PR is included in version 2.0.0-beta.10 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Fix setRange call to vtkDataArray for single component arrays.
There may be cases (such as here) where an explicit call is made to
vtkDataArray::getRange(range, 0)
with index === 0. This can trigger unexpected call to computeRange if setRange isn't called with index === 0 before.