michael-s-molina commented on issue #41779: URL: https://github.com/apache/superset/issues/41779#issuecomment-4904359132
@rusackas I like the idea of improving built-in registration for extensions. Some suggestions to help move this forward: - I think we should exclude anything related to dashboards and their entry points from this SIP as they are already being tacked by @EnxDev's [SIP](https://docs.google.com/document/d/1T0-03Z-3hhXHKJtQtPU5Oq1H1wSJ_SQ7sEOa93I9aFI/edit?tab=t.vkac7hmtjujz) and focus on built-in extensions registration and code organization. - It would be interesting to cover as part of this proposal not only how we handle built-in extensions but also how we organize them in the codebase. - Will we have a dedicated folder or will they be mixed with non-extension code? - Is there any change to code structure given that they have to obey to the same APIs as external extensions? - Do we have a single resolution mechanism or the host invokes each registry depending on the type (views, editors, semantic layers, etc). Keep in mind that the providers have different structures for each type. -- 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]
