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
I think we should not change anything, because we have not been advertising them as "deprecated" but we can start in v2. so I'll remove them from docs and we can mark those attributes as "deprecated" in the schema, but keep them in all the same places they are now bundle-wise
The transforms are a registered method (function) on the plotly API.
It appears we cannot "deprecate" transforms similar to other data attributes by putting it in a _deprecated container.
So I am wondering what is the expected behaviour for deprecating transforms?
Just changing the description similar to what we did for heatmapgl is enough?
Should Plotly.validate pass or it does not matter while there is #4759 bug?!
@nicolaskruchten Hello, i was wondering why the transformers were deprecated and if there is a way to include a similar function (filtering data above a threshold) nativly with plotly?
There is of course the possibility to filter the data outside of plotly, but I would assume it could be faster to do it within the lib?
@nicolaskruchten Hello, i was wondering why the transformers were deprecated and if there is a way to include a similar function (filtering data above a threshold) nativly with plotly?
There is of course the possibility to filter the data outside of plotly, but I would assume it could be faster to do it within the lib?
I'm also looking for some guidance on why transforms are being deprecated and what the recommended alternate method of handling will be.
Activity
nicolaskruchten commentedon May 11, 2021
Let's hold off on this one until we can talk about it next week
nicolaskruchten commentedon May 13, 2021
I think we should not change anything, because we have not been advertising them as "deprecated" but we can start in v2. so I'll remove them from docs and we can mark those attributes as "deprecated" in the schema, but keep them in all the same places they are now bundle-wise
archmoj commentedon May 13, 2021
The
transforms
are a registered method (function) on the plotly API.It appears we cannot "deprecate"
transforms
similar to other data attributes by putting it in a_deprecated
container.So I am wondering what is the expected behaviour for deprecating
transforms
?Just changing the description similar to what we did for
heatmapgl
is enough?Should
Plotly.validate
pass or it does not matter while there is #4759 bug?!nicolaskruchten commentedon May 13, 2021
Yes, including some deprecation text in the schema attributes is enough for me.
Domino987 commentedon Apr 10, 2023
@nicolaskruchten Hello, i was wondering why the transformers were deprecated and if there is a way to include a similar function (filtering data above a threshold) nativly with plotly?
There is of course the possibility to filter the data outside of plotly, but I would assume it could be faster to do it within the lib?
chadamski commentedon May 10, 2023
I'm also looking for some guidance on why transforms are being deprecated and what the recommended alternate method of handling will be.
andoks commentedon Nov 7, 2023
I would also like to know what alternatives there are to the transform functionality
Also I believe this relates to the deprecation notices change in the docs plotly/graphing-library-docs@8b334a9