Replacing FORM_FIELD_TYPES Enum with a Dynamic Table

[MEHRSHAD-MIRSHEKARY]

Currently, the DynamicField model in dj-dynamic-form uses a static FORM_FIELD_TYPES enum (a list of tuples) to define available field types, such as "text", "number", "dropdown", etc. While this works well for a predefined set of options, it limits extensibility for users who might want to add custom field types without modifying the package's source code.

I propose replacing this enum with a dedicated FieldType model (a database table) to make field types dynamic and user-configurable. This change would:

• Allow users to define new field types (e.g., "phone", "multi_select") via the database or admin interface.
• Enable metadata for each type (e.g., description, default validation rules).
• Keep the package lightweight while enhancing flexibility for open-source adoption.

Current Approach

FORM_FIELD_TYPES = [
    ("text", _("Text Field")),
    ("number", _("Number Field")),
    ("email", _("Email Field")),
    ("boolean", _("Boolean Field")),
    ("date", _("Date Field")),
    ("dropdown", _("Dropdown Field")),
]
field_type = models.CharField(max_length=20, choices=FORM_FIELD_TYPES)

Proposed Approach

class FieldType(models.Model):
    name = models.CharField(max_length=20, unique=True)
    label = models.CharField(max_length=255)
    description = models.TextField(blank=True, null=True)

    def __str__(self):
        return self.label

class DynamicField(models.Model):
    form = models.ForeignKey(DynamicForm, on_delete=models.CASCADE, related_name="fields")
    name = models.CharField(max_length=255)
    field_type = models.ForeignKey(FieldType, on_delete=models.PROTECT)
    # ... other fields ...

[ARYAN-NIKNEZHAD]

Yes that is a good idea.