-
Notifications
You must be signed in to change notification settings - Fork 383
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
Record paths handle root-level array indices inconsistently #775
Comments
Related: #651 |
It seems that in v4, the states no longer diverge, I've tested so with the same script as John's in v4:
So this is fixed in v4 since both the local version of the record and the server's have the value However as you can see, the client does not handle properly root level array indices path, resulting in the You can find the script in: https://github.com/deepstreamIO/test-scripts/commit/8361b68fe79f6521fa7ffb0951dbb1a5d0a230ca |
In this script it doesn't look like you wait for the I would recommend connecting another client and doing a snapshot to confirm data is the same between client and server |
Thank you Alex for pointing out the discard timeout option, that escaped my mind. Here is the updated version of the script, which also reveals that the states no longer diverge, so we are only left with the issue of not being able to set a root level array using brackets notation, so statements like
|
Closing in favour of #1046 |
In the js client:
In the example above, local and remote record state diverge due to different handling of the path. The client believes the '[4]' path accesses the fourth index of the array, the server believes the path is invalid.
Perhaps this issue should be raised against the client instead, since it's supposed to replicate the behaviour of the server, but in this case I believe this is a due to a regression in server behaviour.
The text was updated successfully, but these errors were encountered: