👀 Views: 304 💬 Answers: 1 📅 Created: 2025-06-06

laravel pagination api PHP

I've been researching this but I'm working on a Laravel 10 application where I need to paginate a nested resource collection... Specifically, I have a `Post` model that has many `Comment` models. I want to create an endpoint that allows clients to fetch a paginated list of comments for a given post, with the ability to filter comments by their `status`. However, I'm working with issues with the filtering and pagination logic. I set up my controller method like this: ```php public function getComments(Request $request, $postId) { $query = Comment::where('post_id', $postId); if ($request->has('status')) { $query->where('status', $request->input('status')); } $comments = $query->paginate(10); return response()->json($comments); } ``` When I call this endpoint with a GET request to `/posts/{postId}/comments?status=approved`, it returns a paginated JSON response correctly. However, if I try to include a sorting parameter in the query string, like `?status=approved&sort=created_at`, I get the following behavior: `SQLSTATE[42S22]: Column not found: 1054 Unknown column 'created_at' in 'order clause'`. I attempted to add sorting logic inside the `getComments` method like this: ```php if ($request->has('sort')) { $query->orderBy($request->input('sort')); } ``` However, this throws an behavior when the `sort` parameter is provided with an invalid column name. I want to ensure that the sorting only applies to valid columns to prevent this scenario. What approach should I take to validate the `sort` parameter before applying it to the query? Is there a best practice for dynamically allowing sorting on specific columns? Any insights or suggestions would be greatly appreciated! I'm using Php stable in this project. Any suggestions would be helpful.