rusackas commented on issue #33448: URL: https://github.com/apache/superset/issues/33448#issuecomment-3228903311
I've been stewing on this. I'm open to Explore being a component (with props to drive the UI of it) if that's enough to scratch the itch for now, but I also think that there's a pre-requisite here of a long-awaited refactor of our control panels... how they're laid out, how the state works, and how we define/render/load these controls. And that effort, in turn, is continguent upon the work happening in Extensions. I'll write up a SIP about how I think control panels ought to work, and how that migration process can happen, and then I think we ought to tackle that so that the Explore we make portable is indeed the Explore that we want. -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
