Breaking changes to auth branch - meteor-core

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Breaking changes to auth branch
Received-SPF: pass (google.com: domain of t...@thesnail.org designates 209.85.220.49 as permitted sender) client-ip=209.85.220.49;
Date: Tue, 25 Sep 2012 12:33:46 +1000
From: Tom Coleman <t...@thesnail.org>
To: meteor-core@googlegroups.com
Message-ID: <680CFE5EFB864CA2982FE282FC4D7...@thesnail.org>
In-Reply-To: <CAMpkn3g3xy+ZVNg-=qeJZPq4HjkTPrY=DUyzwbmwSRYASYQ...@mail.gmail.com>
References: <CAMpkn3g3xy+ZVNg-=qeJZPq4HjkTPrY=DUyzwbmwSRYASYQ...@mail.gmail.com>
Subject: Re: [meteor-core] Breaking changes to auth branch
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5061180a_490b7c5_ba"

--5061180a_490b7c5_ba
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Nick. 

When you say: 


On Saturday, 22 September 2012 at 8:53 AM, Nick Martin wrote:

> -> If you have any additional fields on your user records that you want visible to the client, you must either explicitly publish them (if you do not want them directly editable by the user) or move them to the 'profile' sub-object (if you do want them editable). 
Do you mean to setup another publication on the users collection? Something like:

  Meteor.publish(null, function() {
    if (this.userId())
      return Meteor.users.find({_id: this.userId()},
                               {fields: {specialField: true}});
    else
      return null;
  }, {is_auto: true});


Cheers,
Tom.

--5061180a_490b7c5_ba
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


                <div>Hi Nick.
                </div><div><br></div><div>When you say:</div>
                <div></div>
                =20
                <p style=3D=22color: =23A0A0A8;=22>On Saturday, 22 Septem=
ber 2012 at 8:53 AM, Nick Martin wrote:</p>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><span style=3D=22color: rgb(0, 0, 0); font-fami=
ly: Helvetica; font-size: 13px; font-style: normal; font-variant: normal;=
 font-weight: normal; letter-spacing: normal; line-height: normal; orphan=
s: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; w=
hite-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjus=
t: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, =
255); display: inline =21important; float: none; =22>-&gt; If you have an=
y additional fields on your user records that you want visible to the cli=
ent, you must either explicitly publish them (if you do not want them dir=
ectly editable by the user) or move them to the 'profile' sub-object (if =
you do want them editable).</span></span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>Do you mean to setup another publication on the user=
s collection=3F Something like:</div><div><br></div><div><div>&nbsp; Mete=
or.publish(null, function() =7B</div><div>&nbsp; &nbsp; if (this.userId()=
)</div><div>&nbsp; &nbsp; &nbsp; return Meteor.users.find(=7B=5Fid: this.=
userId()=7D,</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=7Bfields: =7B=
special=46ield: true=7D=7D);</div><div>&nbsp; &nbsp; else</div><div>&nbsp=
; &nbsp; &nbsp; return null;</div><div>&nbsp; =7D, =7Bis=5Fauto: true=7D)=
;</div></div><div><br></div><div>Cheers,</div><div>Tom.</div>
            
--5061180a_490b7c5_ba--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
