docs: clarify forbidClientAccountCreation requires client+server config #13961
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix forbidClientAccountCreation Documentation Issue
Problem
Users were confused when setting
forbidClientAccountCreation: trueinAccounts.config()only on the server side. While this successfully blocks account creation calls, theaccounts-uipackage still shows the "Create account" link because it only checks the client-side configuration.Solution
Updated the JSDoc documentation for
Accounts.config()to clearly explain:forbidClientAccountCreationparameter explaining it must be set on both client and serverChanges Made
packages/accounts-base/accounts_common.jsExample Usage
Verification
Fixes #13922