David Glasser add4f6e015 Disallow {fields:{_id:0}} in observeChanges ...

This implies it is not allowed in `observe` either, or in cursors
returned from publish functions, or in cursors used in {{#each}}

Why? observeChanges and DDP publication use the ID as part of the
callback/message, and eliding it completely breaks them. Meteor UI uses
the ID with {{#each}} to properly move nodes around instead of
re-rendering. We could try to allow it for `observe` outside of
{{#each}}, but it would feel somewhat inconsistent.

2014-01-06 21:16:23 -08:00

..

.meteor

update docs app to release sso-1

2013-12-20 14:21:59 -08:00

client

Disallow {fields:{_id:0}} in observeChanges

2014-01-06 21:16:23 -08:00

lib

Update docs and examples to 0.7.0.1.

2013-12-20 14:23:11 -08:00

public

Depends on PR 685 (the appcache package).

2013-02-21 18:41:53 -08:00