jansule commented on issue #31932: URL: https://github.com/apache/superset/issues/31932#issuecomment-2626539894
Great proposal! I just want to share my two cents from the perspective of an external visualization plugin developer: - **Dependency management** was quite cumbersome (as it happens on bigger NodeJs projects), especially when sharing common dependencies between the core and (multiple) plugins. Providing a solution for that would be fantastic! - **Provision of common UI elements** that are also extensible. While the superset-ui-core already provides a great set of UI elements, the ones used in the explore view were still heavily adjusted in the core. So as a plugin developer, I had to either make changes to the core (adding custom controls), or redo the UI components in the plugin, in order to get the same look and feel for my custom controls. Devs would benefit from a solution here, allowing us to faster create custom components that better integrate in the UI in the short run, while improving the components' maintainability in the long run. - **Changes that also affect the backend**: Some changes require adjustments to the backend. A very simple case might be adding configuration parameters that need to be passed to the plugins, e.g. API tokens, adjustable default values, etc. Currently, this would require devs to adjust the core repository. Being able to also adjust backend functionality from a third party plugin, would allow me to provide more useful features to a plugin, without having to touch the main repository. - **Connecting to datasources via HTTP** can probably already cover quite a big area besides the SQL based datasources. Especially, when integrating third party sources that do not want to expose their databases to the public, but rather provide access via HTTP APIs. States like Germany follow an open data approach, where governmental bodies have to provide access to public information. This often happens via HTTP APIs (especially in the geographic domain, where these APIs are standardized) which provide sensor data as well as other geospatial information. Being able to integrate these datasources as third party plugins would be extremely beneficial for us. Knowing that these things are not easily solvable problems that also come with considerations regarding applicability as well as security, I hope that the future architecture might address some of these problems. -- 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]
