rusackas commented on issue #39209: URL: https://github.com/apache/superset/issues/39209#issuecomment-5399879533
@mikebridge @gabotorresruiz We've discussed this in the Extensions Working Group previously (and surely can again!). I'm in favor of the migration in general (never been a fan of redux) but the question is of timing (order of operations) and potential "throwaway work." @villebro and @michael-s-molina might want to weigh in here, but I think that fundamentally, Extensions should not care, nor have access to, ANY state management framework of the host application. They should be written to use the extension interface to call for or provide data/hooks specifically passed to or from their interface, and should not care in the slightest that Superset has moved from React to Tanstack or to anything else. If we do the full replacement now, it'll mean rewiring things tied to Redux (e.g. dashboard components) that should not be tied to a state management framework at all. That re-wiring will still need to be gutted as they move to extensions in the near future, so this migration might be more work now than it would be a little down the road. -- 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]
