As part of the release process we'll update docs and all active
examples (other/unfinished examples can be updated as necessary). eg, first to
0.6.1-rc1, etc, and then to 0.6.1 when that is tagged from rc.
Inspired by a pull request from tmeasday (though we've changed the underlying
code enough on ddp-pre1 that I had to rewrite it myself).
Use it in todos. No docs yet, but the Meteor.subscribe docs are already
scheduled for some attention.
Instead of a general client-side sub de-duping mechanism (which mostly existed
for the sake of autosubscribe, and causes issues with server-driven
unsubscribes), make Meteor.subscribe explicitly aware of reactivity.
Expose an "invalidated" flag on Meteor.deps.Context.
Guarantee that invalidation callbacks from different contexts will not be
interleaved at flush time. This has the implication that if you do
context1.onInvalidate(function () {
context2.invalidate();
});
and this is the only way to invalidate context2, then context2's invalidation
callbacks will not be called until after *ALL* of context1's callbacks are
called. This allows us to be sure that the "unsubscribe, unless autorun tried to
re-create an identical sub" logic runs after the autorun function is rerun.
Originally from https://github.com/meteor/meteor/pull/569
Reworked to:
- apply to soma.png, not soma.jpeg (file was previously misnamed).
- don't touch bootstrap's glyph image. It would cause conflicts later, and is not neighborly.
- A new `insecure` package reproduces the experience we had
before this change, in which all collections are by default
totally open to all changes
- With or without the `insecure` package, you can now call
collection.allow() to define which calls to the default
mutator methods should be allowed
- Store login token in local storage so that we log in across tabs
- Simulate local storage on IE 7 using userData
- Expose a {{user}} helper to Handlerbars
- Poll the FB popup so that we know when the user closed it
(still without the new design around this)
- Support logout
- Slightly better error handling (but should still get better)
- Support non-autopublishing collections, and make loginTokens such a collection
