mistercrunch commented on issue #33441: URL: https://github.com/apache/superset/issues/33441#issuecomment-2940870268
Post conversation yesterday, I believe we agreed in many things there: - `@apache-superset/core` becomes the new, clean, official foundation for assets that are shared between the main app - `@superset-ui/core` remains for the time being, and becomes largely private and unsupported for non-supserset-official packages - some things to get migrated from `@superset-ui/core` to `@apache-superset/core`, like `components/` + `theming/` for instance. Maybe more of the clean/settled bits - new identified need to provide a fully typed REST API client as part of `@apache-superset/core`, something generated based on openapi spec the backend is providing. `SupersetClient` in `@superset-ui/core` likely to get phased-out and replaced by that - still a need to refactor/improve `@apache-superset/core`, in some cases as a path to migration to the settled API in `@apache-superset/core`. Say the utils lib could be cleaned up and improved in the old package, and when it's clean and settled enough we move to the new package -- 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]
