Wrapping Meteor.user() seems common enough to design its own little helper. We could provide an API that creates a Store by default, but can be skipped via noStore: true just like createFind.
In the documentation, we should recommend calling createUser just once at the global level, and re-using it (at least without SSR). It doesn't need to be created in each component.
Maybe also createUserId, which is really simple.
Perhaps something similar for accessing Meteor's Session globals?
Wrapping
Meteor.user()seems common enough to design its own little helper. We could provide an API that creates a Store by default, but can be skipped vianoStore: truejust likecreateFind.In the documentation, we should recommend calling
createUserjust once at the global level, and re-using it (at least without SSR). It doesn't need to be created in each component.Maybe also
createUserId, which is really simple.Perhaps something similar for accessing Meteor's
Sessionglobals?