Plotly.deleteFrames(gd, null) should delete *all* frames

[rreusser]

Currently, I think Plotly.deleteFrames('graph', null); will throw an error as it expects a list of frame indices to be deleted. This seems like an oversight. To match animate(gd, null), it should probably delete all frames. If there's agreement, I'll make this quick fix.

will fail here: https://github.com/plotly/plotly.js/blob/master/src/plot_api/plot_api.js#L2767

[etpinard]

Hmm. What does Plotly.deleteTraces(gd, null) do?

[rreusser]

Comparison:

[rreusser]

The challenge (both for traces and frames, IMO) is that it's difficult to track what the indices actually are since there's no API for querying the state of the chart without digging into ._fullData — which is pretty stable at this point though still private — and ._transitionData — which always bugs me as a slight misnomer that should be _animationData so that I hate recommending digging into private data as a formally correct answer to how to maintain the state of the plot.

[rreusser]

(Small addendum that unless no longer throwing an error is a breaking change, I don't see a particular problem with considering both of these an enhancement or both of these simply unsupported (in which case the frame error should be more descriptive))

[etpinard]

@rreusser this issue was closed by #1531, correct? Or do you want to leave this open to discuss it further?

[rreusser]

Oops. Neglected to close. 👍