Keep Request::get() behavior stable despite Symfony deprecation

[yurii-zadryhun]

Symfony 7.4 deprecated Request::get() and plans to remove it in future versions.
Laravel currently exposes Illuminate\Http\Request::get() as a thin proxy to Symfony’s implementation.

This creates two problems:

1. Once Symfony removes the method, Laravel will be forced into a breaking change.
2. $request->get() is widely and historically used across Laravel apps and packages, relying on its flexible precedence behavior.

Given the significant usage, should we decouple Laravel from Symfony’s get by re-implementing the behavior directly in Laravel's get?

This change would allow Laravel to remain forward-compatible with Symfony while preserving long-standing behavior, avoiding a high-impact breaking change.

If we reach a consensus in this discussion that this change makes sense, I’m happy to follow up with a PR.

[AntonPugach]

Yes, this is indeed a very important question, since many projects already use Request::get() and it is critical for their support

[marius-ciclistu]

There were discussions that were against it. Tailor was not sure in making a decision so far.
Laravel is all about input instead of get. If they decide to not copy it from synfony, they should delete the method so that a macro can replace it.