Maybe use control-mergebox instead of meteor-streams

[mitar]

I made a package which allows one to disable Meteor's mergebox in publish functions, but keep all other functionality intact. I think it is cleaner and easier to use it then custom code around meteor-streams.

But, I have not tested it really much, so maybe it does not work as advertised. ;-)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[engelgabriel]

I like the idea. We are studying your package already :)

[Charuru]

Hows it going?

[engelgabriel]

We liked the approach, but I haven't had time to implement and test it.

I believe this kind of ability to turn off the mergebox if coming to Meteor official release soon anyway.

[mitar]

I believe this kind of ability to turn off the mergebox if coming to Meteor official release soon anyway.

Not to my knowledge?

[engelgabriel]

As they move to GraphQL, they said the reactivity all the way from the DB will become optional...

[mitar]

Oh, yes. But that will not be so soon? But yes. :-)