Here's a fairly odd corner case: when the client makes a subscription, the server sends the documents that are currently in the subscription set, followed by subscription ready. Once the client gets subscription ready, it knows that it has all the documents currently available, which means that any other other documents that it has in the browser database are old documents (which were deleted on the server at some point when the client wasn't connected), and so can now be deleted on the client.
But this process only happens after the client has made a subscription. So if the client doesn't make any subscriptions, old documents in the browser database won't get deleted.
Which I'm not sure if there's anything to do about given the goal of following the Meteor API. But it does look weird when testing.
Here's a fairly odd corner case: when the client makes a subscription, the server sends the documents that are currently in the subscription set, followed by subscription ready. Once the client gets subscription ready, it knows that it has all the documents currently available, which means that any other other documents that it has in the browser database are old documents (which were deleted on the server at some point when the client wasn't connected), and so can now be deleted on the client.
But this process only happens after the client has made a subscription. So if the client doesn't make any subscriptions, old documents in the browser database won't get deleted.
Which I'm not sure if there's anything to do about given the goal of following the Meteor API. But it does look weird when testing.