Need clarification on query strings with Laravel

You can do this:

Route::post('/post/{post}/comments', 'CommentController@store');

And in store method on controller:

public function store(Post $post)
{
  // You have now access to $post model
}

@morteza not to be rude but I am already aware of that. I am just noticing some people still use query strings over such URL structures with Laravel, and I'm wondering why.

Typically, any required parameters would be in the path. Any optional parameters (like filters) are query strings.

So, most people use query strings for paginations, sorting, filtering, searches, etc.

If you are following restful principles then you would have specific routes like /edit and then add query strings for variant data that you need to pass to the same route rather than create new routes.

So, as thomaskim says, things like filters and paginators. You are still hitting the same resource but you have some additional information to pass along

Parameters or query string either way works.