-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accounts.onCreateUser issue #17
Comments
I've made it so that it doesn't warn unless you actually use the hook, But I guess you mean we make it possible to have multiple onCreateUser() in an application, wouldn't that be better if this solution came from accounts-base instead? 💃 |
Yeah either one these three solutions (only warn if the hook if used, run both the hook and the original callback, fix the problem at the root) works for me, since I'm not using the hook anyway :) |
Alright, would it be a big issue if removed the serverside version of the hook? Just now it's causing more issues than it is solving, when one already can use onCreateUser for the same thing, maybe just document how to do this in the Readme without and then remove the hook? |
Sounds good to me. |
You can only have a single callback hook on
Accounts.onCreateUser
, which leads to the following warning:What if instead of showing that warning,
accounts-ui
simply extended the current callback (available atAccounts._onCreateUserHook
) with its own custom logic?i.e.
The text was updated successfully, but these errors were encountered: