{"action":"created","issue":{"url":"https://api.github.com/repos/englue/meteor-publish-composite/issues/42","labels_url":"https://api.github.com/repos/englue/meteor-publish-composite/issues/42/labels{/name}","comments_url":"https://api.github.com/repos/englue/meteor-publish-composite/issues/42/comments","events_url":"https://api.github.com/repos/englue/meteor-publish-composite/issues/42/events","html_url":"https://github.com/englue/meteor-publish-composite/issues/42","id":88827996,"number":42,"title":"Feature request: restrict which cursors are published","user":{"login":"Diggsey","id":451321,"avatar_url":"https://avatars.githubusercontent.com/u/451321?v=3","gravatar_id":"","url":"https://api.github.com/users/Diggsey","html_url":"https://github.com/Diggsey","followers_url":"https://api.github.com/users/Diggsey/followers","following_url":"https://api.github.com/users/Diggsey/following{/other_user}","gists_url":"https://api.github.com/users/Diggsey/gists{/gist_id}","starred_url":"https://api.github.com/users/Diggsey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Diggsey/subscriptions","organizations_url":"https://api.github.com/users/Diggsey/orgs","repos_url":"https://api.github.com/users/Diggsey/repos","events_url":"https://api.github.com/users/Diggsey/events{/privacy}","received_events_url":"https://api.github.com/users/Diggsey/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-06-16T20:09:51Z","updated_at":"2015-08-11T21:19:24Z","closed_at":null,"body":"At the moment, everything returned by a top-level \"find\" is automatically published to the client, but I only want the children to be published.\r\n\r\nSimilarly, sometimes you only want certain fields to be published, but you need all the fields to run the child query. For example, I have a field `user.secret` which I use as part of a child query, but I don't want to publish that field to the client.\r\n\r\nThe first feature can be implemented by an option \"internal: true\" or similar, the second by adding a field specifier to the options, eg. \"fields: { secret: false }\""},"comment":{"url":"https://api.github.com/repos/englue/meteor-publish-composite/issues/comments/130080937","html_url":"https://github.com/englue/meteor-publish-composite/issues/42#issuecomment-130080937","issue_url":"https://api.github.com/repos/englue/meteor-publish-composite/issues/42","id":130080937,"user":{"login":"reywood","id":1796302,"avatar_url":"https://avatars.githubusercontent.com/u/1796302?v=3","gravatar_id":"","url":"https://api.github.com/users/reywood","html_url":"https://github.com/reywood","followers_url":"https://api.github.com/users/reywood/followers","following_url":"https://api.github.com/users/reywood/following{/other_user}","gists_url":"https://api.github.com/users/reywood/gists{/gist_id}","starred_url":"https://api.github.com/users/reywood/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/reywood/subscriptions","organizations_url":"https://api.github.com/users/reywood/orgs","repos_url":"https://api.github.com/users/reywood/repos","events_url":"https://api.github.com/users/reywood/events{/privacy}","received_events_url":"https://api.github.com/users/reywood/received_events","type":"User","site_admin":false},"created_at":"2015-08-11T21:19:24Z","updated_at":"2015-08-11T21:19:24Z","body":"It relies on the private function `_compileProjection` which doesn't seem like a great idea. The Meteor folks could refactor or remove that function at any time. It also completely removes the `observeChanges` handler which is a major blow to performance in the default use case. Given these issues, I think PR #43 is a non-starter."}}