-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trackProperties
method in immutableStateInvariantMiddleware.ts
is not correctly managing the circularity
#4843
Comments
I create a PR to fix this: #4844 |
Hi. No approval or reject ? |
It's low on the priority list atm - all of us maintainers have been busy with other things the last few weeks. We'll try to take a look when we get a chance! In the meantime, you could disable the default version of the immutability middleware, paste the modified version into your app, and add that to the store instead. |
trackProperties
method in immutableStateInvariantMiddleware.ts
is not correctly managing the circularity
I also have this same issue. |
Can someone validates the PR ? |
I think the CI failures have been putting people off - I'll try rebasing the PR to see if the CI failures still happen. |
Same. Are the unit tests passing without my change ? |
yes - i rebased #4864 today and its CI is passing fine. |
The PR seems to break things, and I don't have the time to investigate why. It does seem to be related to the If someone can debug it further, figure out why this breaks things, and fix it, we can look at merging this, but it's not on my priority list at this point. |
@paztis I just discovered the problema and fix it. You have complete solution in: |
https://github.com/reduxjs/redux-toolkit/blob/master/packages/toolkit/src/immutableStateInvariantMiddleware.ts#L57
recursive call to trackProperties (line 57) is not passing down the checkedObjects argument.
It means all the circularity check you do in your code is totally bypass.
That's why immutable is not working with circular references
The text was updated successfully, but these errors were encountered: