Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow per-backend user pipeline settings #677

Merged
merged 2 commits into from
Jul 15, 2024
Merged

Allow per-backend user pipeline settings #677

merged 2 commits into from
Jul 15, 2024

Commits on Jul 13, 2024

  1. Allow per-backend user pipeline settings 

    According to
https://python-social-auth.readthedocs.io/en/latest/configuration/settings.html,
"All settings can be defined per-backend by adding the backend name to
the setting name, like SOCIAL_AUTH_TWITTER_LOGIN_URL". This changes
user.py to actually use per-backend settings for options like
USERNAME_IS_FULL_EMAIL.

Note that get_username is always called with a backend, but user_details
isn't, so a different version of `setting' is needed for the two.
    @dehnert
    dehnert committed Jul 13, 2024
    Configuration menu
    Copy the full SHA
    45f2913 View commit details
    Browse the repository at this point in the history

  2. [pre-commit.ci] auto fixes from pre-commit.com hooks 

    for more information, see https://pre-commit.ci
    @pre-commit-ci
    pre-commit-ci[bot] committed Jul 13, 2024
    Configuration menu
    Copy the full SHA
    6e250e1 View commit details
    Browse the repository at this point in the history