These are chat archives for reactioncommerce/reaction
@jshimko, Jeremy, recently you leaved a comment about
Tracker.Component. And this is quite interesting because yesterday I've started to think about switching from
komposer to something else. Did you look at other
tracker realization like currently MDG default and especially what do you think about
The problem with
komposer - it reruns on every
props change which is terrible. I've noticed that just yesterday. How do you think other
Tracker realizations also have such "side effect"?
Tracker.Component. There’s very little code behind it (~50 lines), so it’s pretty easy to understand what’s going on at first glance. And setting up your data in components looks very similar to the old Blaze style template-level stuff in onCreated hooks (
createContainerhas is they are just one big autorun wrapper around potentially several reactive dependencies. So if any of those deps change, the entire thing runs again.
Tracker.Componentlets you define as many separate
this.autorun’s as you want. So only the ones that change will re-run (at least that’s my understanding of it).
Illustrates the UI impact of lumping all reactivity into a single autorun vs isolating them like we did in Blaze.
meteor deploy <subdomain>. Is that expected/supported?
Errors prevented deploying: While linking the program: error: reactioncommerce:reaction-logger is not compatible with architecture 'os.linux.x86_64'