Keep Request::get() behavior stable despite Symfony deprecation
#58249
Replies: 3 comments 9 replies
-
|
Yes, this is indeed a very important question, since many projects already use Request::get() and it is critical for their support |
Beta Was this translation helpful? Give feedback.
-
|
There were discussions that were against it. Tailor was not sure in making a decision so far. |
Beta Was this translation helpful? Give feedback.
-
|
The reason get is deprecated acc to brave search is: get can be changed to reorder the logic based on the verb. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Symfony 7.4deprecatedRequest::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:
$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
getby re-implementing the behavior directly in Laravel'sget?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.
Beta Was this translation helpful? Give feedback.
All reactions