4 ms·

I was in the firebase beta, and it really was pretty simple to get a new app up and running, there was certainly good documentation. What are you referring to?

drhayes9 13y ago
I can't find answers to these questions in the docs, had to stumble around with the library first: - be sure to set an empty object on your scope before setting up implicit binding on that object. If you don't, the error will be cryptic. - add the property "authRequired: true" to your routes when setting up your $routeProvider to get AngularFire to block access to that route when not authenticated. - be careful about using $scope.apply with AngularFire since you're often already in the apply cycle in its callbacks (would be nice if that were explicit).
- joshstrange 13y ago
  This is nitpicky for sure but angularFire doesn't play nice with AngularJS 1.2's breaking out some modules (Route, Sanitize, Cookies, and 1-2 more) into separate JS files. I had to comment out all the $route stuff in angularFire so that I could get them to work together. Thankfully I am not using fireBase with my $route's so I am unaffected. Also, I'm sure some of you might point out 1.2 is still in an RC state but I needed ngAnimate and didn't want to have to re-write a bunch of code a few weeks from now when it releases it's final version.
WhitneyLand 13y ago
To start, there are two different api methods for setting up data binding between angular and firebase. Where is a good semantic/conceptual explanation of the difference?
- drhayes9 13y ago
  Agreed, the labels they use are a little imprecise. "Implicit" is a two-way, automatic binding: updates from the server will show up in your app and updates your app makes will be sent to the server automatically. "Explicit" is a one-way, manual binding: updates from the server will show up in your app automatically but you have to sync back to the server manually using the add, remove, and update methods. Is that what you mean?
  - WhitneyLand 13y ago
    Yes, thanks. The problem is certain operations work differently depending on the mode, and you end up having to do debugging/source code digging to really understand it, which is a frustrating waste of time.

drhayes9 13y ago

I can't find answers to these questions in the docs, had to stumble around with the library first: - be sure to set an empty object on your scope before setting up implicit binding on that object. If you don't, the error will be cryptic. - add the property "authRequired: true" to your routes when setting up your $routeProvider to get AngularFire to block access to that route when not authenticated. - be careful about using $scope.apply with AngularFire since you're often already in the apply cycle in its callbacks (would be nice if that were explicit).

joshstrange 13y ago
This is nitpicky for sure but angularFire doesn't play nice with AngularJS 1.2's breaking out some modules (Route, Sanitize, Cookies, and 1-2 more) into separate JS files. I had to comment out all the $route stuff in angularFire so that I could get them to work together. Thankfully I am not using fireBase with my $route's so I am unaffected. Also, I'm sure some of you might point out 1.2 is still in an RC state but I needed ngAnimate and didn't want to have to re-write a bunch of code a few weeks from now when it releases it's final version.

WhitneyLand 13y ago

To start, there are two different api methods for setting up data binding between angular and firebase. Where is a good semantic/conceptual explanation of the difference?

drhayes9 13y ago
Agreed, the labels they use are a little imprecise. "Implicit" is a two-way, automatic binding: updates from the server will show up in your app and updates your app makes will be sent to the server automatically. "Explicit" is a one-way, manual binding: updates from the server will show up in your app automatically but you have to sync back to the server manually using the add, remove, and update methods. Is that what you mean?
- WhitneyLand 13y ago
  Yes, thanks. The problem is certain operations work differently depending on the mode, and you end up having to do debugging/source code digging to really understand it, which is a frustrating waste of time.