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 Jul 15, 2023. It is now read-only.
I have an untested branch that has this working, but wanted to know if you'd be interested in this before we pose a PR.
in short, firebase has support for saving lists of data via their push()function (as opposed to update()). this allows us to tack on object for a user has many <foo> date. right now the save()function only accommodates a regular firebase update()
since you need to get a reference to the original child object first, the proposed interface is:
// wherein `entry` is a new has-many object // and `userId` is the child it will be pushed tocontroller.storage.users.push(userId,entry)
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.
I have an untested branch that has this working, but wanted to know if you'd be interested in this before we pose a PR.
in short, firebase has support for saving lists of data via their
push()
function (as opposed toupdate()
). this allows us to tack on object for auser has many <foo>
date. right now thesave()
function only accommodates a regular firebaseupdate()
since you need to get a reference to the original child object first, the proposed interface is:
The text was updated successfully, but these errors were encountered: