Skip to content

Clarified attribute mapping docs. #424

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dino8890
Copy link

@dino8890 dino8890 commented Jul 26, 2025

PR related to the issue #334.

The current documentation makes it seem that attributes will be mapped to "profile" object if configured. In Django parlance, "profile" typically refers the model related to the User via OneToOneField.

Excerpt from Django docs:

If you wish to store information related to User, you can use a OneToOneField to a model containing the fields for additional information. This one-to-one model is often called a profile model, as it might store non-auth related information about a site user. For example you might create an Employee model:

This is not the case, and this changes makes it clear that attributes will be mapped to the User model only, including custom User models if configured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant