fix: merge static and dynamic extended profile fields

[johanseto]

Description

Summary

Route extended profile fields to the correct storage in the account API instead of indiscriminately combining model-backed fields with UserProfile.meta.

extended_profile_fields acts as the allowlist for account API profile extensions. For each configured field, the API checks whether its name is a concrete field on the model configured by PROFILE_EXTENSION_FORM:

• Model-backed fields are validated and written through the extension form to the model.
• Configured fields that are not model-backed are written to UserProfile.meta.
• Fields not listed in extended_profile_fields are ignored by the account API and are not included in extended-profile validation.

Reads use the same field classification: model-backed fields come from the extension model, and dynamic fields come from UserProfile.meta. If the user does not yet have an extension-model record, configured static fields can still be read from meta as a compatibility fallback. When a model record exists, its values are authoritative for model-backed fields.

Test

#Example Configuration

Settings:

PROFILE_EXTENSION_FORM = "custom_reg_form.forms.ExtraInfoForm"

REGISTRATION_EXTENSION_FORM_FIELDS_TPA_OVERRIDES = ["arabic_name", "national_id"]

Tenant config settings:

    "extended_profile_fields": [
        "hobby",
        "sport",
        "arabic_name",
        "national_id",
        "occupation",
        "movie"
    ],

Check the get of the data in the following endpoint.
Validate the static data - > extension profile form model
and dynamic data -> meta from profile data is retrieved.
http://local.openedx.io:8000/api/user/v1/accounts/admin

Before

After

[johanseto]

Related with
nelc/frontend-app-account#16

[johanseto]

extended_profile_fields control:

Screencast.from.30-09-26.09.48.29.webm