Closed aboire closed 1 year ago
Published in v1.8.2
@aboire can you please look into #167? It seem to have started happening after this. So far I have not been able to identify where exactly things get broken, so if we don't resolve this quickly I will have to reverse this PR early next week.
@StorytellerCZ Do you know how to reproduce the error? I asked for more information on the issue
I will try to get minimum reproduction up some time.
I think if you get socialize:feed
package, and then on your opening page subscribe to socialize.feed.friendsPosts
with data from feed posting it will throw on server.
@StorytellerCZ if you understand correctly, it is that it is no longer parallel which creates the problem because at the time of unpublish the children the entry this.documents[docId] is deleted before going through all the chidrens so I think when replacing in _publishChildrenOf "for of" by "Promise.all" that should solve the problem
I believe some tests could have been added as part of this feature. Great to see this implemented though!
Forum reference: https://forums.meteor.com/t/reactive-publish-using-async-collection-functions/61470
What
Add the possibility that "find" and "children" are async
Why
With Meteor async migration, there may be cases where awaiting for results is needed inside the callback.