Meteor Guide is quite clear on
Rather than dealing with the specifics of this field, it can be helpful to just ignore its existence entirely.
As discussed in the Collections article, Meteor’s data transfer protocol doesn’t do deeply nested diffing of fields, so it’s a good idea to flatten out your objects into many top-level fields on the document.
So what is the recommended way to store user related data?
- Store them in not-too-deep user fields (custom, other than profile)? How deep can they be? Is
user.workDays.monday.startsok or too deep?
- Create related Collections?
- … something other?
I’m looking forward to read your suggestions