added an "exists" attribute to differentiate whether we have data or not

[christophe-g]

follows discussions #33.

[phrohdoh]

Doesn't this imply the data in memory does not reflect what is in Firebase?

If that is the case then this isn't helpfully in the case of [] which could very well exist in either location and be valid.

[christophe-g]

Thanks,
http://stackoverflow.com/questions/15408416/how-to-handle-empty-arrays-in-firebase : "there is no way to force empty array into firebase".

And yes, data in memory does not always reflect what is in Firebase - see discussion #177 (zeroValue).

[mbleigh]

Would you consider adding a statusKnown property to this PR in addition to exists? Right now you're having to use a three-value boolean (null, false, true) to track state which feels off to me. Ideally I'd prefer statusKnown which indicates whether data has ever been received for the current path, and exists which indicates whether it's null.

[christophe-g]

Thanks a lot for looking at this and merging #166 and #167.

Makes perfect sense to add a statusKnown attribute. Should land shortly.

[christophe-g]

Landed

[andrewspy]

Any update on merging statusKnown attribute?

[christophe-g]

Seems the codebase diverted quite a bit and this PR would need to be rebased against master. I'll do that once #213 is merged.
C.

[christophe-g]

Closed by #234