Alternative Event Tracking: withTrackedReducer

[rainerhahnekamp]

Summary

This PR introduces withTrackedReducer as an alternative approach to tracking reducer-based state changes in Redux DevTools. It addresses limitations in the original withEventsTracking implementation.

The original implementation (based on #231) attempted to automatically track reducer-based state changes via the glitch tracker. However, this approach has fundamental limitations that cannot be resolved with the specified approach.

Several edge cases are documented in the skipped tests within with-events-tracking.spec.ts.

This PR introduces an alternative way, where end users have to use the wrapperd function withTrackedReducer which calls internally updateState using the event's name.

If we proceed with this approach, the following items need to be completed:

• Update documentation to explain withTrackedReducer usage and when to use it vs withReducer
• Update demo applications to showcase the new API
• Remove or deprecate code from the initial withEventsTracking approach (if applicable)
• Add validation/runtime checks to ensure withTrackedReducer is only used with stores that have devtools and glitch tracking enabled

[michael-small]

I did a preliminary review for now and will give a more formal one in the evening. Looks good though.

One piece missing at the moment: some sort of documentation reference

[rainerhahnekamp]

@michael-small @wolfmanfx

I see it as temporarily. In the end, we need support for meta-reducers in the core...

[michael-small]

I see it as temporarily. In the end, we need support for meta-reducers in the core...

In that respect, I think this code/approach as-is minus the outstanding items seems legit. But with those outstanding items, I defer to @wolfmanfx on the outstanding considerations. I imagine there will be some more reviewing opportunity then.

[wolfmanfx]

@rainerhahnekamp I have updated / cleaned the branch. I also vote for the temp solution with the "withTrackedReducer".