mistercrunch commented on issue #33441: URL: https://github.com/apache/superset/issues/33441#issuecomment-2932361792
I think we all agree there's a need to have a bucket of components/utils/frameworks shared across the ecosystem of packages and use cases (main app, plugins, extensions, embed). Today that package is pretty much `core/` and `chart-controls/`. If you unpack what's in there today you env up roughly with this list: - things required to build viz plugins - utility functions shared across plugins/packages/main-app - peerDeps generally reused in plugins/extensions - some test utils - chart components to do react native "embeds" - failed or semi-failed experiments (dynamic plugins, chart-oriented storybook) Now we have the option to clean/refactor `core/` or start over on a new name and carefully migrate things from core/ to that new package. I think I could be convinced in either approach, but generally hate multi-year transitions. Why not cleaning up core and making it what it needs to become (?) -- 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]
