You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating the wallet to support BigInt output values, a new error started appearing in the console:
This is more a warning than an error, this is what the linked docs says:
It is highly recommended that you only put plain serializable objects, arrays, and primitives into your store. It's technically possible to insert non-serializable items into the store, but doing so can break the ability to persist and rehydrate the contents of a store, as well as interfere with time-travel debugging.
If you are okay with things like persistence and time-travel debugging potentially not working as intended, then you are totally welcome to put non-serializable items into your Redux store. Ultimately, it's your application, and how you implement it is up to you. As with many other things about Redux, just be sure you understand what tradeoffs are involved.
Even though this error is being displayed, since apparently we don't use those features, everything seems to be working. The QA is passing.
However, we should investigate how to fix this. Ideally we can configure a custom serializer and deserializer for the Redux state, and we can use our custom BigInt parser and stringifier for that. The second option would be to simply try to disable this error.
The text was updated successfully, but these errors were encountered:
After updating the wallet to support
BigInt
output values, a new error started appearing in the console:This is more a warning than an error, this is what the linked docs says:
Even though this error is being displayed, since apparently we don't use those features, everything seems to be working. The QA is passing.
However, we should investigate how to fix this. Ideally we can configure a custom serializer and deserializer for the Redux state, and we can use our custom
BigInt
parser and stringifier for that. The second option would be to simply try to disable this error.The text was updated successfully, but these errors were encountered: