Skip to content

Commit 1fe427d

Browse files
committed
refactor: rename variable for clarity in extended profile saving process
1 parent f139c09 commit 1fe427d

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

  • openedx/core/djangoapps/user_api/accounts

openedx/core/djangoapps/user_api/accounts/api.py

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -399,11 +399,11 @@ def _update_extended_profile_if_needed(
399399
# 2. For new profiles, the user field isn't in the form data
400400
# 3. We need to assign the user programmatically before the database save
401401
# 4. If we called save() directly, it would fail with integrity errors for new profiles
402-
extended_profile_model = extended_profile_form.save(commit=False)
403-
if not hasattr(extended_profile_model, "user") or extended_profile_model.user is None:
404-
extended_profile_model.user = user_profile.user
405-
# Now persist the model with the user field properly set
406-
extended_profile_model.save()
402+
extended_profile = extended_profile_form.save(commit=False)
403+
if not hasattr(extended_profile, "user") or extended_profile.user is None:
404+
extended_profile.user = user_profile.user
405+
# Now persist the instance with the user field properly set
406+
extended_profile.save()
407407
except Exception as e: # pylint: disable=broad-exception-caught
408408
logger.error("Error saving extended profile model: %s", e)
409409

0 commit comments

Comments
 (0)