Collection.find doesn't call map when result is empty about meteor-rxjs HOT 3 CLOSED

@ppoliani
If there is no data in the Mongo.Collection, then the changes events won't fire, and the next callback of the Observable won't fire.
You can use RxJS startWith operator in order to solve it:

Collection.find(condition).startWith([]).map(x => ....)

Also, make sure to call subscribe on the Observable that map returns, otherwise the teardown logic of the Observable won't run (or, use the Observable with async Pipe of Angular 2):

Collection.find(condition).startWith([]).map(x => ....).subscribe((data) => {
     // ...
});

from meteor-rxjs.

I personally expected it to return an empty array when nothing was in the collection or at least a null. Is there a reason why it doesn't do this by default?

from meteor-rxjs.

I agree with @jerradpatch Otherwise, there is no way to distinguish between the two cases (data isn't loaded yet vs data is loaded but empty)

It is needed to avoid showing users the empty placeholders in lists, which is confusing (user sees a notice saying that her list is empty, and then the list populates with data)

There is a pull request fixing it #103

from meteor-rxjs.