You should try to use this.userId for most of the times. Try to avoid called Meteor.user() on the server. It’ll fetch the user object from Mongo, everytime you invoke it.
no that cannot work, becouse of the context. this.userId() doesnt exists in this context.
currently i reovled it by injecting user id into the record during the query operation where i have access to user context.
Not elegant solution but it works, i hope there’s a better way to do this.
I can get user info without problem in query/mutation operations, but I’m trying to resolve the record of type Event that has a property named “state”. In that context i dont have access to the user info.