BE-Register events to meet

[MarisiaS]

This PR addresses issue #51

Implementation

1. backend/api/models.py

Implemented the MeetEvent model with the following fields:

• meet: This is a foreignKey to SwimMeet. Set on_delete to cascate because swim meet is our principal data.
• group: This is a foreignKey to Group. Set on_delete to Protect to be mindfull of num_event.
• event_type: This is a foreignKey to EventType. Set on_delete to Protect to be mindfull of num_event.
• num_event: IntegerField

Added a unique constrain to meet and num_event

2. backend/api/migrations/0012_meetevent_meetevent_unique_num_event_meet.py

Generated with command makemigrations.

3. backend/api/serializers/MeetEventSerializer.py

• Created MeetEventSerializer based on ModelSerializer to display almost all the information about an event.
• Created MeetEventPatchSerializer based on ModelSerializer to display only num_event.

4. backend/api/views/MeetEventView.py

Created an APIView named MeetEventView with:

• get method to list all the events associated with a given swim meet sorted by num_event. This view uses the MeetEventSerializer.
• post method to add a new event to a given swim meet. This view also uses the MeetEventSerializer.
• patch method to delete a event from a given swim meet and update the num_event for the next events. This view uses the MeetEventPatchSerializer.

5. backend/api/urls.py

Added the following endpoint:

• meet_event/<int:meet_id>/ uses MeetEventView.

Swagger

All new endpoints are accessible through Swagger. Each endpoint has been tested successfully, including listing all events associated with a swim meet, adding an event to a swim meet, and deleting an event from a swim meet.

[MarisiaS]

Could a meet have more than one record of the same event type associated?

I think that's ok because they could have semifinal and final for the same event. But maybe then we should add an extra identifier to the name.