René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"open items uncovered during Plotly.react push","articleBody":"Some rules that were good ideas before but become crucial with `Plotly.react` so that we recognize a non-change correctly:\r\n- Never create new arrays in the `supplyDefaults` step - for example reshaping 1D to 2D arrays. That should be done in a `calc` step and NOT pushed back into `_fullData`.\r\n- Don't modify attributes after finishing `supplyDefaults`, unless you're going to push the results back to the input (`data`/`layout`) as well, like `autorange`/`range`.\r\n- When you're stashing things on `_full*`, always make `_private` attributes.\r\n\r\nMost of the instances of this are taken care of in #2341, but a few are open:\r\n- [ ] `tick0`, `dtick` -\u003e default filled in late (After SD) - also for tickmode=array, not needed at all\r\n- [ ] `camera` doesn’t push back into `_fullLlayout` after drag, only `layout`?\r\n- [ ] tests for `scatter3d` with uneven or missing x/y/z\r\n- [ ] tests for `surface` with uneven, missing, or ragged x/y/z\r\n- [x] `autocolorscale`: first time it gets set on, second time off - is that intentional? cauto sometimes shows a similar effect… see `gl3d_scatter-color-mono-and-palette` **resolved in:** https://github.com/plotly/plotly.js/pull/3341\r\n- [ ] `contourcarpet`: `zmin`/`zmax` get filled in (after `supplyDefaults`) but they aren't actually attributes of `contourcarpet`. They should be!\r\n- [ ] `autorange: 'reversed'` should get replaced in `layout` once it has been acted on. There's a polar mock where this doesn't happen until the second draw.","author":{"url":"https://github.com/alexcjohnson","@type":"Person","name":"alexcjohnson"},"datePublished":"2018-02-08T22:56:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/2353/plotly.js/issues/2353"}