Fix bad index lookups in remove and update
Merge pull request #8 from ThomasWeiser/gh-pages

Bugfix: angularFire() returned undefined when value is already cached.
Make service dependencies explicit to allow minification
Add minified version (0.1.0)
Use directive for auto-scrolling behavior
Allow no callback parameter on .add()
Log type mismatch instead of resetting data
Explicit check for undefined instead of !
Another instance where we mean undefined, not false
Use Angular $parse service to assign values in $scope

Simple variable assignment in _resolve works correctly only with scalar variables. When the synchronized value is referenced as "name['key']" or "a.b.c[10]", then $watch tracks the changes in $scope.name['key'] or $scope.a.b.c[10]", but updates from Firebase would reflected to $scope["name['key']"] or $scope["a.b.c[10]"].
The modified code uses Angular $parse to assign the corrected variable within the $scope even if it belongs to an object or array.
Merge branch 'gh-pages' of https://github.com/Newtrin0/angularFire into Newtrin0-gh-pages
Merge pull request #15 from thomasboyt/gh-pages

Chat refactor & .add() bugfix
Add braces
Merge pull request #9 from BinaryMuse/patch-1

Fix bad index lookups in remove and update
Merge branch 'gh-pages' of github.com:firebase/angularFire into gh-pages
Change examples to avoid double binding on $scope
Fix broken indexes on remove.
Notice that removeChild removes the index,
so updateIndexes will always get undefined as
the 'from' parameter. As a consequence,
the indexes never get updated on remove.
This can be reproduced in the following way:
remove the 0th element from a collection,
this will cause the index go inconsistent,
and consequent removals will lead
to a broken state.
This is a trivial fix that I tested
to fix the problem in my use case.
Merge pull request #22 from reebalazs/gh-pages

Fix broken indexes after remove
Add query support, closes #21
Honor limit if provided to angularFire via reference