michael-s-molina commented on issue #26229: URL: https://github.com/apache/superset/issues/26229#issuecomment-1860459079
> I would vote for implementing the best library for a particular visualization. Any technical decision is always a trade-off. Any time you introduce a new library you need to consider all base logic that needs to be supported consistently throughout the app. Think about theming, tooltip handling, legend interaction, zooming, data transformation, etc. If you introduce a new library you need to implement these behaviors in a consistent manner with the rest of the plugins, to avoid decreasing UX. At times, you want to introduce a new library because it provides many important features that are not supported by the common library and the cost of implementing the base logic pays off. I generally use the principle where if you can provide the plugin in a satisfactory manner using ECharts, that should be the preferred way. Only when this is not an option, I would introduce a new library. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
