I'm pretty new to laravel and trying to create my first app.
I have three different classes: User, Activity and Lecture.
Users are capable of creating an activity and lecture.
Every activity has its technical manager, product manager and activity manager, and users are capable of enrolling the activities.
Every lecture has its lecturer and users are capable of enrolling the lecture.
I want to create the eloquent relationships necessary but I'm not sure if the users should belong to the activity or vice versa. I have accomplished one of my goals (creating a relationship between users and activity managers) however, I'm confused with the rest of it and feel like it is not the best way to achieve my results.
In that moment, my code looks like that:
App\Activity :
class Activity extends Model
{
protected $guarded = [];
public function TechnicalManager(){
return $this->belongsTo('App\User','technical_manager');
}
public function ActivityManager(){
return $this->belongsTo('App\User','activity_manager');
}
public function ProductManager(){
return $this->belongsTo('App\User','product_manager');
}
public function Enrollers(){
return $this->belongsToMany('App\User','user_activity');
}
}
App\User :
class User extends Authenticatable
{
use Notifiable;
public function activities(){
return $this->belongsToMany('App\Activity','id');
}
}
If you plan on using Eloquent's relationships, then the idea would be:
I see nothing wrong with writing relationships on both sides of a model, as long as you use them. If you're not going to use them, then why have them?
Image the situation:
Find a user, it's activities and who is the technical manager and the activity manager for the activities
User::with(['activities','activities.TechnicalManager','activities.ActivityManager'])->find($id)