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
{{ message }}
This repository has been archived by the owner on Aug 25, 2018. It is now read-only.
This may be more a question than a feature request, but:
I shortly realized that this plugin automatically adds an ID (similar to "-KecHZh3...") to new models, so certain backbone-methods (such as model.isNew) may won't work anymore... Is there a clever, more native way to check whether a model/Firebase-collection has already been synchronized, such as model.synced()?! As of now you could reach such functionality by e.g. hooking into the sync-function, but that's not the best solution in terms of performance because changing a model's (pseudo-)attribute (like "synced") from false to true will result in another request... Any ideas, plans?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This may be more a question than a feature request, but:
I shortly realized that this plugin automatically adds an ID (similar to "-KecHZh3...") to new models, so certain backbone-methods (such as model.isNew) may won't work anymore... Is there a clever, more native way to check whether a model/Firebase-collection has already been synchronized, such as model.synced()?! As of now you could reach such functionality by e.g. hooking into the sync-function, but that's not the best solution in terms of performance because changing a model's (pseudo-)attribute (like "synced") from false to true will result in another request... Any ideas, plans?
The text was updated successfully, but these errors were encountered: