Ok that makes sense, but shouldn’t that reactivity only ‘react’ when the URL changes? When I visit the note page, the console fires off twice. Shouldn’t it only fire once since I only visited a URL this one time?
1 First the template loads.
-> first log (so this is not because of reactivity, just the template gets rendered)
2 Then the subscription becomes ready
-> second log (this is reactive on the find() call)
3 If you would change the url
-> third log (reactive on flow router)
In general it’s not an issue that some things are rendered multiple times, I would not worry too much about it. Also because you should not do heavy tasks in helpers anyway so it would just be updating a simple var. Nothing to worry about.
Finding out why it’s doing it can be tricky because reactivity is not instantly visible in the code. You need to know which things are reactive and which are not.
@lucfanken - You say that you should not do heavy tasks in helpers. This sounds completely logical, but as a meteor newb, where should the heavy tasks be offloaded to? I’m having the same issue as @sergiotapia but I have some heavy tasks and this multiple-time processing latency is compounding quickly.