-
Notifications
You must be signed in to change notification settings - Fork 24
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
.remove method seems to leave stale data behind? #16
Comments
Hey, thanks for reporting this! Basically what Regarding the old contents being returned after new contents are set, that's unexpected indeed! I'll need to dig into this to reproduce the issue. |
I'm not sure if this is something I'm doing wrong, or if there's a bug somewhere...
Basically I have a test suite that cleans up after itself.
At the beginning of the tests, we do something that looks like this:
At the end of the tests I do something like this:
No errors get thrown.
Yet after setting anything on
permissions
alias, the old state returns:Even manually
idx.set('permissions', null)
won't do the trick for me either - seems to just not do anything.PS:
I know it's a bit weird that I have a
permissions
object as a nested layer inside thepermissions
collection in the IDX root - the idea here is that (eventually) I'll replacepermissions
with some DocID, so that if I want to add/remove permissions from this list, I can just update that associated doc without touching the IDX root. I think this will just make the migration a bit smoother and help avoid breaking changes.The text was updated successfully, but these errors were encountered: