michael-s-molina commented on issue #33441: URL: https://github.com/apache/superset/issues/33441#issuecomment-2934851212
> Also did some more thinking on the public/private segmentation and semver implications, but thinking that if we were to take what's in core today, clean the crap out of it, clarify the public/private intersection, and do proper semver packaging, that one package could fulfill the vision to support all external use cases (viz plugins, extensions, chart-embed, ...) This is exactly the same conclusion we had. We named this package `@apache-superset/core` because it does not only include UI elements but also utility functions, APIs, types, etc. Our thinking was to start a fresh package and move the vetted components from the existing packages to it, which would avoid crap and clarify the public/private intersection as you mentioned. In the end, the `@superset-ui` packages would be removed, public things would be consolidated into `@apache-superset/core`, and private things would be organized into other packages. -- 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]
