amitmiran137 opened a new issue #17210: URL: https://github.com/apache/superset/issues/17210
## [SIP-76] Proposal for Dynamic dashboard components ### Motivation Today there is a very narrow list of components that can live within a dashboards: charts, Row , column , tabs, header, markdown and divider as part of our dashboard requirements at Nielsen we want to add another non-chart component that shows a summary of the active filters within the dashboard for display purposes as described in [here](https://github.com/apache/superset/issues/17118) but shortly we understood that it would be hard to get those accepted and aligned with the superset community and adding such component would require maintenance and burden overtime. ### Proposed Change So we decided on a less invasive approach that allows adding custom dashboard components into the dashboard similar to the plugins system that exists for charts and native filters today each custom component will have access to the dashboard state and would be able to leverage its state. the advantage here, comparing the filter summary bar is that dashboard components can be written externally to superset and will not be part of the superset-frontend system which will keep it stable similar to custom plugins, it will be up to the developer to integrate those components into superset and load them into superset they way they see fit ### New or Changed Public Interfaces setupDashboardComponents.ts file would be a file in which you would register your custom components in the following approach ``` import dashboardComponentsRegistry from '../visualizations/presets/dashboardComponents'; export default function setupDashboardComponents() { dashboardComponentsRegistry.set('test', test); } ``` ### Migration Plan and Compatibility ### Rejected Alternatives creating dashboard components directly into the superset source code like the following PR: https://github.com/apache/superset/pull/17153 -- 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]
