Incorrect ordering while using `singleEvent` as `true`

Since setting singleEvent as true returns the whole set of data in a single response as a value:Object containing all the values i.e {key1:val1, key2:val2,...} (existing behavior) rather than value:Array<Object> i.e [{key:key1, val:val1}, {key:key2, val:val2},...] (expected behavior), the order becomes inconsistent while iterating through the result object.

[EddyVerbruggen]

@JillevdW Looks like this is fixed in plugin version 8.0.0 (out soon). The order in the JSON object is now as specified as in the orderBy clause (on Android this was already the case), and I’ve added a new children property to the result object which is an array. Docs updated.

[JillevdW]

@EddyVerbruggen that could be true, I’m not sure, however that would imply the query function is not the same as the function I just posted, some observations:

• In the Swift function, the snapshot function contains all the results from the query in an array. As such, the callback is only called once (not entirely true, since I use the function .observe which observes value changes as well, but it will still return all the items in one call, even on subsequent calls).
• singleEvent set to true returns all the results from the query bundled into an object.
• singleEvent set to false calls the callback once for every single item returned from the query.

So if what you say is correct, there is still a difference between the native behaviour and the way the interface here exposes them, perhaps that is not really relevant to anyone that hasn’t used the native library, but it is relevant here since we lose the order of elements when using singleEvent = true.