Deprecation warning since symfony/http-foundation 7.4: for Request::get()

[mariopro]

Laravel Version

10.40.2

PHP Version

8.3.1

Database Driver & Version

No response

Description

After the composer update, laravel/framework" was updated to 12.40.2 and is now throwing a deprecation warning Since symfony/http-foundation 7.4: Request::get() is deprecated, use properties ->attributes, query or request directly instead. in /home/theproject/public_html/vendor/symfony/deprecation-contracts/function.php on line 25

Steps To Reproduce

To reproduce:

1. Perform a composer update and check that it updates to laravel/framework 12.40.2
2. If not done yet, do a composer dump-autoload
3. Check the logs
4. Go to a specific page where you have the code like Request::get()->('something') or $request::get()->('something') or request()->get()->('something') and replace it with $request->something or request()->something and the deprecation warning no longer appears.

EDIT/UPDATE (December 1, 2025)

Not a framework bug

After digging into a clean Laravel installation, this is not a Laravel/framework bug or issue. It´s in fact a Symfony deprecation for the Request methods used. For people using packages or their own code, they shold review any request()->get() or $request->get() code that need to be changed. Please refer to Symfony documentation at https://symfony.com/blog/new-in-symfony-7-4-request-class-improvements

[crynobone]

Hey there, thanks for reporting this issue.

We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?

Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.

laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.

Thanks!

[mariopro]

Please note that what I reported is not a bug but a deprecation warning. As I´ve mentioned in the report, doing a composer update to get Laravel 12.42.2 and activate the "Logging Deprecation Warnings" (https://laravel.com/docs/12.x/logging#logging-deprecation-warnings)
You can look at the code that triggers the deprecation warning in vendor/symfony/http-foundation/Request.php.
It´s not a bug, but it should be in the Laravel Documentation Release Notes for 12.40.2 since it may require some refactoring for $request->get('something') or request('something') that needs to be changed to fix the Symfony deprecation warning.
Many packages will have to be updated, for instance, "yajra/laravel-datatables-oracle".

[crynobone]

We can only fix the issue if laravel/framework itself uses deprecated feature. Otherwise, you need to notify 3rd party package to fix the issue.

Our integration tests so far hasn't show this specific warning so we do need a reproduction repository if this indeed require changes to laravel/framework.

[Spir]

Here is how to handle it:

    // use this if the value comes from route placeholders or custom attributes
    $value = $request->attributes->get('some_key');

    // use this for GET query parameters
    $value = $request->query->get('some_key');

    // use this for POST-submitted data
    $value = $request->request->get('some_key');

as per:
https://symfony.com/blog/new-in-symfony-7-4-request-class-improvements

[mariopro]

@Spir I´ve done it on all my projects. That’s the way to solve it, but Laravel/framework, in fact, does not trigger a deprecation warning—only some first- and third-party packages do. Thanks for posting it here, as it may help others 😉

[Spir]

By the way if you want to check is a param exists you will have to do this:

if ($request->query->has('parameter')) {
    dd($request->query->get('parameter'));
}

[Spir]

Laravel/framework, in fact, does not trigger a deprecation warning—only some first- and third-party packages do

Actually Laravel is not responsible for this. It's just a wrapper. I'm currious how this will be handled since it may do some breaking changes. Anyway I think the upgrade make the code more clear. request()->get('something') was too clueless where the data came from.

[Spir]

Sorry for spamming but there deprecation notice doesn't really help to fix any bug:
LOG.warning: Since symfony/http-foundation 7.4: Request::get() is deprecated, use properties ->attributes, query or request directly instead. in vendor/symfony/deprecation-contracts/function.php

Do you have any idea how to get more details?

[mariopro]

Hi @Spir , that deprecation warning only happens if the code doesn´t meet the new Symfony Request settings for the request()->get('someparameter') or $request->get('someparameter'). It can be solved by refactoring to request()->someparameter, $request->someparameter.
It doesn't help to fix, but you have posted above the solution that is in Symfony´s documentation. That is enough, and the deprecation warnings go away (unless there is some package in the vendor/ directory that is still using the old request methods, which is the case, for instance, with yajra/laravel-datatables and others).
Enabling the deprecation logs https://laravel.com/docs/12.x/logging#logging-deprecation-warnings will log the places where the deprecations are happening.

[deshazer]

For our situation converting from

// Old
$request->get('some_key', 'default_value')  // the "symfony way"

to

// New
$request->input('some_key', 'default_value') // the "Laravel way"

was the best solution. We only cared about checking the request's query and POST body. Hope that helps someone 👍