The intended result is that if you are holding a piece of data, and you have a dep for it, you can ask the global dependency server whether it has changed by sending the key and version. The main benefit of this approach is that the application server doesn't need to be aware of which queries each client is currently tracking - the client can keep that knowledge for itself, reducing the burden on the server and giving the developer more options for controlling when new data is fetched.
So, basically, we're long-polling?
I will be at tonight's meetup if anyone wants to have a go.
like
meteor create simple-todos-angularcd simple-todos-angularmeteoropen http://localhost:3000
meteor add angular
modify code in simple-meteor-angular.html
modify code in simple-meteor-angular.js
meteor update
meteor update dburles:mongo-collection-instances
meteor update lai:collection-extensions
METEOR LONDOOOOOON
whats the hashtag for this group or twitter handle?
or better
#meteor #london
so that it appears in both the meteor and london searches
@rapidexpert ^
a walkthough on getting bootstrap 4 set up with meteor 1.3
the npm run script way
Some tips for anyone moving a React project over to 1.3, if you do
meteor remove react it'll also remove react-meteor-data which you might want to add back in, and since jsx compiles to js, you need to import React from 'react' wherever you're using ReactDOM, even if not using React yourself.
