MatthewFlamm

I haven't read this in detail yet, but it might be useful to have Algorithm classes for this. We could reuse them inside the filter methods too. This would further...

This looks good to me in general. It looks like we have to wait for a new codespell version to be released to implement this, or semi-dangerously move to a...

I fixed codespell, but I'm not sure flake8 supports pyproject.toml. see https://flake8.pycqa.org/en/latest/user/configuration.html#configuration-locations and this package https://github.com/john-hen/Flake8-pyproject. I know nothing about this later package other than it claims to fix this...

Doing a bit more digging, it looks like the maintainer(s) of `flake8` is(are) decidedly against supporting configuration in `pyproject.toml`. See https://github.com/PyCQA/flake8/issues/234. I think there are some good points in favor...

```py mesh = grid.contour([0.5], np.ravel(np.random.randn(dims[0], dims[1], dims[2])), method='marching_cubes') ``` In pyvista, the first dimension has the match the number of points or cells. So you need to flatten or ravel...

> Alternatively, could there be a check for the array size and try to infer the intended shape automatically? This would be great, but it probably has some nasty edge...

I'm going to put this as a good-first-issue. I _think_ we are suggesting that we could check for multidimensional data and then provide a more helpful error message in the...

Take a shot and please ask questions either here or in the slack channel if you need pointers.

This issue was specifically for `vtk_points`, which is used in that module. If you want to open more PRs to add more test coverage for PointSet and _PointSet that would...

I think there should also be the inverse check to what has been implemented, i.e. if a parameter is documented as optional/default then check that the parameter has a default...