Avoid loading Django user models before apps are ready #3386
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.
To register a custom Provider, users subclass
allauth.socialaccount.providers.base.ProviderAccount
. Their subclass is then registered usingallauth.socialaccount.providers.registry.register(MyProvider)
.The registration must happen before the
allauth.socialaccount
app models are ready, as theSocialApp.provider
choices come from the registry. Otherwise, a Django migration is created because at the time of the import ofallauth.socialaccount.models
, the registry was empty, but when the models are ready (and Django can check migrations) the registry contains the custom provider.Below is an example stack trace to illustrate the issue:
Submitting Pull Requests
General
Examples:
"fix(google): Fixed foobar bug"
,"feat(accounts): Added foobar feature"
.ChangeLog.rst
.AUTHORS
.