-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate transforms in v2 #5652
Comments
Let's hold off on this one until we can talk about it next week |
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 |
Yes, including some deprecation text in the schema attributes is enough for me. |
@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. |
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 |
We should remove
transforms
from the bundles but keep a way to re-include them.The text was updated successfully, but these errors were encountered: