I’m all for it in general… but there are a lot of things in Superset that can 
and should be Extensions providing/requesting things through their extension 
interface rather than through ANY underlying state management library. Until 
things like Dashboard components are de-coupled from Redux accordingly, this 
seems like it’ll be rewiring a whole lot of things that should be un-wired 
first. This may lead to instability due to the migration, where I’d prefer to 
see decoupling and reduced dependency on Redux prior to migrating it. This can 
be brought up at the next Extensions working group sync, but I believe 
Extensions (i.e. much of Superset in the near future) should have no knowledge 
of or dependence on Redux or its replacement(s).

+0 for now, but happy to discuss more… if this is timed right, safe, and fits 
the current Extensions architecture decisions in flight, I could be swayed.

Thanks, and looking forward to a Redux-free future as much as anyone, I promise.

-e-

Evan Rusackas
On Aug 20, 2026 at 4:54 AM -0700, Mehmet Salih Yavuz <[email protected]>, 
wrote:
>
> +1 (binding)
>
>
> Mehmet Salih Yavuz
>
>
> On Thursday, August 20th, 2026 at 12:32 AM, Gabriel Torres 
> <[email protected]> wrote:
>
> > Hi all,
> >
> > I'd like to call a vote on SIP-207 Replace Redux with Zustand and TanStack
> > Query
> >
> > This proposal introduces a clear separation between two fundamentally
> > different kinds of state that are currently handled by the same tool: UI
> > state (edit mode, active tabs, modal visibility; things that live only in
> > the browser) and server state (charts, dashboards, datasets; things that
> > originate from the API and need caching and invalidation). We propose
> > adopting Zustand for UI state and TanStack Query for server state, retiring
> > Redux.
> >
> > The vote will remain open for at least 72 hours, or until the required
> > number of votes has been reached.
> >
> > Please vote accordingly:
> > [ ] +1 Approve
> > [ ] +0 No opinion
> > [ ] -1 Disapprove (please provide reasoning)
> >
> > GitHub Issue: https://github.com/apache/superset/issues/39209
> >
> > Thanks!
> >

Reply via email to