michael-s-molina commented on PR #35259: URL: https://github.com/apache/superset/pull/35259#issuecomment-3335072587
> Note: another option I mentioned before would be to treat superset-core as 100% private, and have something like a superset-extension-sdk as the thing that's public/semvered, it would import/re-export the bits of superset-core we want to actively expose (and maintain) as a public API. I think we're achieving the same objective but through different means. The `superset-core` contains only the bits we want to actively expose and the host application contain the private parts. The private parts don't need to be separate package, they are part of `apache-superset` package already. Correlating with your example, `superset-core` is what you're calling as `superset-extension-sdk` but it's not only for extensions. It can be used by embedded and MCP tools. -- 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]
