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
Right now, the construction of fig2 involves the re-validation of all of the properties in fig1. But this is unnecessarily since the properties are guaranteed to be valid in fig1.
Here, go.Scatter should not rerun the marker validation logic, and go.Figure should not rerun the scatter trace validation logic.
We should have a fast performance path for these cases that just performs a deepcopy on the raw dict and splices that into a new object, without any additional validation.
Hi - we are currently trying to tidy up Plotly's public repositories to help us focus our efforts on things that will help users most. Since this issue has been sitting for several years, so I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our backlog. Thanks for your help - @gvwilson
Consider the following:
Right now, the construction of
fig2
involves the re-validation of all of the properties in fig1. But this is unnecessarily since the properties are guaranteed to be valid in fig1.Also consider this case:
Here, go.Scatter should not rerun the marker validation logic, and go.Figure should not rerun the scatter trace validation logic.
We should have a fast performance path for these cases that just performs a
deepcopy
on the raw dict and splices that into a new object, without any additional validation.See https://community.plot.ly/t/how-to-copy-figure-or-trace-object-deepcopy-no-longer-working/12166
The text was updated successfully, but these errors were encountered: