You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be worth adding a test that guarantees that for all trace types there's clearly defined behaviour for just {type: 'type'} as the entry in data... Basically we don't need to show anything, but we also can't raise an error and we do need a full entry in fullData that allows the editor to populate its widgets etc.
Activity
archmoj commentedon Dec 14, 2018
@nicolaskruchten Your demo is working well with 1.41.2; but not using 1.42.0.
etpinard commentedon Dec 14, 2018
It's probably from #3044 (to was released in 1.42.0).
Can I ask, what's the expected behavior?
etpinard commentedon Dec 14, 2018
For sure, we want
newPlotandreactto result in the same graph, but how should that graph look like?archmoj commentedon Dec 14, 2018
@etpinard Could you please try this demo
nicolaskruchten commentedon Dec 14, 2018
same as an empty scatter or other trace... it should get added to fullData etc... right now the editor gets wedged.
nicolaskruchten commentedon Dec 14, 2018
It might be worth adding a test that guarantees that for all trace types there's clearly defined behaviour for just
{type: 'type'}as the entry indata... Basically we don't need to show anything, but we also can't raise an error and we do need a full entry infullDatathat allows the editor to populate its widgets etc.fixes #3336 - don't try to makeCalcdata on visible:false traces
Merge pull request #3343 from plotly/histogram-first-visible-skip-emp…