okorin/cmp

Community Mentorship Program web

Okorin

Directory where i put public stuff somewhat?

cmp's Issues

Integration of events into the database

So it seems like we have the basic User/Role/Cycle tables configured for the most part.
Obviously we would also want to store event data here along with contest entries, right?
Proposed implementation ER-graph:

Feedback is welcome. It's the first real database I designed. I wanted to separate contests and discussions out of events due to how major they are, and they all have their own unique content anyway. This lets us still create events that are neither contests nor discussions. Event_has_Gamemode refers to one event being able to support multiple gamemodes, but not necessary all of them. Event_Participants is simply a table for everyone who participated in the event somehow, including entrees, judges, organizers, discussion hosts etc. which are all elements of the EventRole table.

EventRole is reserved for roles that are strictly event-based and don't require all the field information that a generic Role does. It's possible that we could just combine these if this distinction is deemed unnecessary, though. A single event participant can be both a judge for, say, osu!mania and an entree for osu! at the same time, or a guest difficulty creator at the same time, which is why including it as a foreign key in Event_Participants is necessary. Some fields for example in User can be missing or have an incorrect Not Null check value, but don't pay attention to those as I wasn't clear on what to make of those in the initial prototype version yet.

Real-time feed of "Beatmap Events"

Possibly a hidden container only visible when hovering your mouse over a button/box in the top or left/right side of the screen.
Will contain a feed of Qualifications, Disqualifications and Ranking beatmaps.

This one query will fail if the hierarchy is taken by another role

RoleController@update: check will succeed and update will fail if the hierarchy level is already taken as is by another role because the DB field is unique

also if it fails it'll just redirect to a blank page cuz it's only going to do something in the last line

public function update($id, Request $request) 
	{
		$role = Role::findOrFail($id);
		$this->authorize('update', $role);
		$request->validate([
			'name' => 'required',
			'description' => 'required',
			'color' => 'required|max:6',
			'hierarchy' => 'required',
		]);
		$role->name         = e($request->name);
		$role->description  = e($request->description);
		$role->color 		= e($request->color);
		$role->hierarchy    = e($request->hierarchy);
		if ($role->save()) return back();

	}