User profile is not created when account is created with accounts-password about docs

[laosb]

Solution: Update docs to explain it.

[abernix]

This conflicts with the concept of https://guide.meteor.com/accounts.html#dont-use-profile and #61.

Essentially, don't use profile. Closing, but reopen if you feel differently. ;)

[MaxPleaner]

It does already say this in the accounts-multi doc here

The default create user function simply copies options.profile into the new user document. Calling onCreateUser overrides the default hook. This can only be called once.

There are two issues I see:

1. The main thing which was non-intuitive to me, which is that onCreateUser overwrites instead of acting as a callback. I suppose I am to blame for not reading the docs before using the method, but still, I don't see this behavior being a feature.
2. The notion that profile should not be used. Reading through the explanation of why it's not a good idea (the default write permission and the fact that people put arbitrary config data there), I see those as good points, but I'm not sure they outweigh the benefits, namely:
   1. the ability to get the username when using a 3rd party service, i.e. accounts-github
   2. the fact that it's intuitive and easily discoverable when poking around the Meteor.user() object

If profile needs manually configured access rules, then perhaps there should be a builtin warning about it. As it stands, though, unless one reads through the doc entry for each method they use (probably a good idea, but uncommon) then they will inevitable have to stumble upon this error in a manner similarly to that of myself: googling "meteor no user profile", reading through an issues thread, then following a link to the docs.