Thanks! Yeah, I was first thinking that this should also go into the URL like the other parameters, but it probably makes more sense to persist it in localStorage because it's likely a setting you don't want to have to change again every time you navigate to one of the rules pages anew. However, we have the same kind of situation in the Targets page, where the equivalent parameter is currently stored in the URL (&showEmptyPools=0|1). It would be good if we made them consistent. So probably the Targets page parameter should also use localStorage then (but a separate key).

Done, maybe funny that we have showEmptyPools and hideEmptyGroups. Should I change hideEmptyGroups to showEmptyGroups and revert its default value?

Done, maybe funny that we have showEmptyPools and hideEmptyGroups. Should I change hideEmptyGroups to showEmptyGroups and revert its default value?

Oh right, let's do that and make it consistent.

Also, I noticed one other thing that I totally missed earlier: I think these settings should not be listed in the global settings menu, as they are already controllable inline on the page itself. All the other settings in that menu are only in there because I wanted to avoid having too many UI knobs on the individual pages. And in that case, maybe these new settings shouldn't even be part of the global Settings Redux slice at all (using Redux for all this is a bit questionable anyway, I had other plans for it initially and then things got chaotic 😅), but we could just use a local useLocalStorage() for these settings in the component itself, like we do here:

Does that make sense?

I updated the PR to use useLocalStorage. It is so much smaller now. Very nice

👍 Looks really nice now, thanks! :)