and for example retrieve data startAt("20150101").endAt("20150105") to a
variable: "data". Then it is possible to accidentally delete the data in
updating root "20141231", by making changes and saving the whole root to
firebase, eventhough that action shouldn't even happen when using this
retrieved scope. Now this can be handled from app-layer, by not making the
action or making manual updates or checks for it, it's in no way firebase
bug, but a feature. My question is that is it possible to prevent this
kinda behaviour / action or is it possibily upcoming? In production a small
bug can easily make a lot of damage, if a bug like this gets in.
Fortunately the app I noticed the issue in hasn't made production yet :).
I noticed that in angular it can be quite a pain-in-the-ass, if you 3-way
bind a data using startAt and endAt, then you accidentally alter data
outside that scope. What happens is that even though I try to update the
data and not delete, it naturally deleted the data that hasn't been fetched
and binded to angular variable.
You received this message because you are subscribed to the Google Groups "Firebase + AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-angular/9cf56ae4-cf78-4820-8d56-73afa1c16df0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.