Contact information

[RignonNoel]

We want to allow each organization that use Volontaria to define some custom field they can use on different resources.

Expected behavior

• Administrators can add custom fields on different resources
• Custom field can be required
• Custom field can have custom validation
• Custom field can be of different type

Current behavior

We have no metadata and no custom field available, it will be a new feature.

Potential solution

Here is a potential UML solution:

N.B: customized_type can be done with a generic foreign key
N.B 2: A validation should be done to validate the generic foreign key is made on a supported type of resource (Event, Position and User to begin)

Here is a minimal (but not complete) checklist that could be use to create the solution:

• Create a CustomField new model
• Create a new serializer mixin that will be used to check CustomField related to the serializer.model attributes value
  • The fields are automatically added into the generated JSON
  • The fields are automatically validated during create() and update() method execution
• Add the serializer mixin to the User, Event and Position serializer to make a proof of concept