How to add new field on Meteor.users?


#1

I want to add new field offices on Meteor.users like this:

Accounts.createUser(
            {
                username: 'admin',
                password: '123456',
                profile: {
                    firstName: 'Theara',
                    lastName: 'Yuom',
                    gender: 'M'                    
                },
                email: 'yuom.theara@gmail.com',
                offices: ['001', '002']
            }
        );

but can’t.


#2

Please clarify “can’t” in this context. Remember that offices aren’t published to the client unless you subscribe to it (or use the autopublish package).


#3

I don’t remove autopublish


#4

You should use the profile key on the user object, which holds an object to describe more information about the user. See this:


#5

@timw is correct. The profile field is the only one you should modify for a meteor user. An easy way of doing this is like so:

Accounts.onCreateUser(function(options, user) {
    if (user.profile == undefined) user.profile = {};
    _.extend(user.profile, { offices : [] });
});

If you don’t have the underscore js library (which is fantastic), you could always do:

user.profile.offices = [];

#6

My mistake, autopublish does only publish "username, profile, and any fields in services" from the users collection, so you need to use the publish/subscribe procedure.


#7

I disagree. The docs says the following:

A user document can contain any data you want to store about a user. Meteor treats the following fields specially:

  • […]
  • profile: an Object which the user can create and update with any data. Do not store anything on profile that you wouldn’t want the user to edit unless you have a deny rule on the Meteor.users collection.
  • […]

It does not encourage you to only use the profile field.


#8

@Peppe_LG: At the same time, wouldn’t you agree that for the “rapid prototyping” use case, this is a true statement? While autopublish is a part of the the application, it doesn’t make sense to modify any other field because then you have to write a custom publish. And when you are outside of the “rapid prototyping” stage and writing a publish statement, would you rather publish just the username, profile, and services, or would you rather whitelist every field you need and then rewrite all of your code that accesses those fields?

You are correct in stating that the documentation says nothing about which fields to modify. Therefore, I modify my previous statement to be, “IMHO, the profile field is the only one you should modify for a meteor user”


#9

@jchristman, I mostly agree with what you’re saying. While prototyping, do whatever you want (the quicker the better), but for a real application, I do see use cases for adding new fields instead of extending the profile field. For example, you may want to store information about the user the user should’t be able to see.


#10

could we add new field out of profile like roles package?


#11

@Peppe_LG agreed. @theara, adding a new field can be done like this:

Accounts.onCreateUser(function(options, user) {
    _.extend(user, { someField : 'initialValue' }); // OR user.someField = 'initialValue';
});

#12

I would advise against storing anything in profile, even during prototyping phase. See this hackpad.


How to wait for the Meteor.users collection gets ready in a library?
#13

@Steve, I don’t see the harm in storing private user information in it, such as theme settings, desired number of items/page, etcetera. If a hacker changes these, it only falls back on himself.

Sure, he can try to bring down your app by successfully writing big amount of useless data in the profile field, but if he’s out to get you, that seems like a pretty poor attempt.


#14

@Peppe_LG: there is no harm in using profile. What is annoying is that it is a special case, an exception in the overall Meteor picture. So I think it is best to advise newcomers to not using it (until it is removed from Meteor).


#15

I think this is exactly how you decide whether or not to store your additional information in profile. If you want it on the client, why wouldn’t you put it on profile?


#16

how to update outside add fields from ios swift


#17

Here is my code, which works well to me:

Accounts.onCreateUser(function(options, user) {
  return _.extend(user, {...options});
});