Skip to content
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

Allow for key changes #326

Closed
ClickerMonkey opened this issue Jun 27, 2016 · 0 comments
Closed

Allow for key changes #326

ClickerMonkey opened this issue Jun 27, 2016 · 0 comments
Assignees

Comments

@ClickerMonkey
Copy link
Member

in putRemoteData - instead of triggering error on key change - detect it and once the key is applied - trigger an event. The model will have to be removed from the all map, models collection, relation collections, and dependents maps and then added back with the new $$key. Maybe instead of removing and adding back (in the case of collections) add an updateKey(old, new) function.

Add tests that verify relationships update their FK, their dependents map and collection keys should be updated. A ModelCollection should listen for key update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant