A way to exclude the state of specific features from being sent to Redux DevTools

[NickBarrett]

I love Fluxor! I use it extensively in my projects.

I love to use Fluxor.Blazor.Web.ReduxDevTools as well. In my largest project however, there are so many features with so much state that the app really slow down. There are quite a few features who's state I don't really need to see in Redux DevTools. In fact, often, it is just the state of the features I'm working on at the time that I need to see.

It would be great if there was a way I could tell Fluxor.Blazor.Web.ReduxDevTools to exclude a feature so its state wasn't sent to ReduxDevTools. Alternatively only select the features I want to include.

Thanks for your consideration

Nick

[mrpmorris]

That would screw up the state when you used the time-travel feature though wouldn't it?

I suppose that's a price you'd have to pay though?

[NickBarrett]

That would be fine for me as I don't use the time-travel feature, but I see this could be confusing to users who were not aware of the constraint.

[mrpmorris]

Have you tried the Diff tab in the ReduxDevTools window?

I think that is what you need.

[NickBarrett]

The issue is more the amount of data that's being passed to Redux DevTools. Both in size and frequency.

I currently have 49 features. Around half of them get initialised at the start with various list data. If I call UseReduxDevTools() it takes minutes to load the app, whereas without it, a couple of seconds. Sometimes it just times out and the page reloads.

I have been playing around with my own adapted version of Fluxor. I've added a bool GetIncludeInReduxDevTools(); to IFeature which get its value from public bool IncludeInReduxDevTools { get; set; } = true; that I added to FeatureStateAttribute. Then in ReduxDevToolsMiddleware, in the GetState() method, I've added the where clause Where(x => x.GetIncludeInReduxDevTools()).

Then, when defining my features, I add the parameter to the attribute like [FeatureState(IncludeInReduxDevTools = false)].

I've also added if (Store.Features.Values.Any(x => x.GetIncludeInReduxDevTools())) return; to the start of OnJumpToState in ReduxDevToolsMiddleware to disable all time travel.

This is working quite well. I can limit which features send state to Redux DevTools to just those that I'm working on at the time.

I figure this is very niche, so if you don't feel it is a fit for Fluxor then I'm happy to close this issue and maintain my own adapted version.

[mrpmorris]

I don't like having a reference to the name "ReduxDevTools" in the core Fluxor library because RDT is browser/web based, and the core Fluxor library is agnostic as to the UI.

Perhaps I could check for [Browseable(false)] on the feature state

[mrpmorris]

Give 6.8.0-Beta1 a try.

There is a DebuggerBrowsable property on FeatureAttribute that you can set to false.

[NickBarrett]

Works great thanks 👍

[mrpmorris]

Stick with the beta for now, I will put it into the next full release.

[mrpmorris]

6.8 full version is released now. This change introduced a bug that has been fixed, so I recommend upgrading (otherwise no routing state in RDT).