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

Overwriting priorities if they already exists #116

Closed
anantn opened this Issue Sep 10, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@anantn
Contributor

anantn commented Sep 10, 2013

angularFire is overwriting priorities if they were already set on server data. Presumably this happens in the case where we call set() which overwrites priority. We should use setWithPriority() and double check that calling update() doesn't overwrite priorities.

@shmert

This comment has been minimized.

Show comment
Hide comment
@shmert

shmert Sep 24, 2013

Agreed, I'm new to AngularFire, but I would like to bind the name of my items to their priority. I don't see a simple way to do this.

$scope.$watch('client.name', (newValue) -> fb.setPriority(newValue) if newValue != undefined)

shmert commented Sep 24, 2013

Agreed, I'm new to AngularFire, but I would like to bind the name of my items to their priority. I don't see a simple way to do this.

$scope.$watch('client.name', (newValue) -> fb.setPriority(newValue) if newValue != undefined)
@anantn

This comment has been minimized.

Show comment
Hide comment
@anantn

anantn Dec 12, 2013

Contributor

We now automatically set priority via the "$priority" property on all objects in v0.5.0 of AngularFire which is now merged into master.

Contributor

anantn commented Dec 12, 2013

We now automatically set priority via the "$priority" property on all objects in v0.5.0 of AngularFire which is now merged into master.

@anantn anantn closed this Dec 12, 2013

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