reviewdevs

I was thinking that Spatie would give me more flexibility along with Policies, like saying

// In CourseController

public function getAllVideos(User $user, Course $course) { 
    self.authorize('getVideos', $course);

    return $course->videos;
}

and then in a CoursePolicy.php file i'd say

public function getVideos(User $user, Course $course)
{
	return $user->hasRole('super-admin') || $user->hasRole('tutor') && $course->author->is($user) || $user->hasRole('learner') && $user->purchasedCourses->has($course);
}

this is more verbose and clear about the intent of what am trying to do

but am not sure if that respects the open closed principle because what if i wanted to make a new role like a subscribed user, i'd have to go to this function and edit it

but at the same time, if i wanted to add a new role and some permissions to it, i'd do that easily from a dashboard or something

however if I go with a middleware approach

i'd just say

public function handle($request, Closure $next)
{
    if ($request->user() && $request->user()->type != 'admin')
    {
        return new Response(view('unauthorized');
    }
    return $next($request);
}

and assign that middleware on some route

which is easier, but not can't be set from a dashboard

so that was confusing me and i thought of asking for some opinions and maybe some tips

Hello, am trying to make something like Udemy as practice after finishing some courses here on Laracasts

I'm trying to fix a problem where I want to allow users who purchased a course to view it, if not, they get 401

I was thinking of two approaches, either using Policies combined with Roles and permissions

like saying

if user can view any course, then respond to him with the courses videos

else, check if user has this course in his purchased courses, then send him the course videos

else, unauthorized

that was the the Policies + roles & permissions approach

but i read that u can do so with Middlewares and it seemed easier to do it with middlewares from this article

https://justlaravel.com/middleware-laravel-content-restriction-user-role/

so i was wondering if someone could explain to me which is better and more scalable in the future

thanks a lot!

I wanted to make roles and permissions to be as dynamic as possible, here is what I made on Diagram.io

https://drive.google.com/file/d/1NNyFpZZLiIhQwFgVnX26dgm-v7Ar8Th_/view?usp=sharing

however I was wondering how would I handle if user is authorized to do some action in Laravel

If anyone is using Laravel 8 and faced a problem with the Unit test where it doesn't understand what is $this->faker->sentence

change this line in the Unit test file

from: use PHPUnit\Framework\TestCase; to: use Tests\TestCase;

@app_dev thanks a lot, I just found out there was a tab on Laracasts called Journey with steps of how to learn more, I skimmed through PHP and OOP since I already know both, and currently am learning building birdboard through TDD, only skipping front end part and replacing it with Restful APIs

@app_dev thank u for replying, What i meant is am not interested in building the website's frontend, I meant that am only interested in building Restful APIs so i don't want to waste time building UI, so am looking for topics that explains just that

Hello, I'm an iOS Developer with 3 years of experience, I wanted to shift to backend and build only restful apps without doing any HTML nor CSS as I would prefer my front end to be building the iOS apps and not websites

So I was wondering which topics should I see on Laracasts, thanks :))