Semi-opinionated event structure

[bwaklog]

This issue is WIP

Motive
The current design of the backend is made to support a specific structure to an event. It follows a hard coded team based structure

type Participant struct {
	Team  string `json:"team"`
	Theme string `json:"theme"`

	Name      string `json:"name"`
	Email     string `json:"email"`
	Phone     int64  `json:"phone"`
	College   string `json:"college"`
	Branch    string `json:"branch"`
	PesHostel string `json:"pesHostel"`
}

This reduces flexibility as all events need to register these specific data per participant. While the current structure does allow individual participant models to be stored, they are logically stored as a team consisting of a single participant.

The server running the backend for an event is limited to only a single event. The RPS for a single event only increases during key checkpoints, which means a server should be able to handle a few more events simultaneously. The current backend works on a single event.db sqlite file.

This issue has a core dependency with the front-end that should be able to send an appropriate request for registering events with their associated event.

Goals

• Remodelling the event relationship
• Handle a flexible event structure that is sent over from front end
• Parser for an dynamic event structure
• Handling multiple events simultaneously