[HttpKernel] [MapQueryString] added key argument to MapQueryString attribute #59157
+28
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
[#MapQueryString]
, the default resolver uses the$request->query-all()
function but there's currently no way to pass a specific key to this function if needed.This PR add a
$key
argument to the#[MapQueryString]
attribute that will allow to pass a specific key if needed to the default resolver.Example :
Given the following query :
https://example.org?search[term]=foo&search[category]=bar
, using current#[MapQueryString]
implementation will resolve an object with only$search
property.Change proposed in this PR allows to pass a
key
argument like#[MapQueryString(key: search)]
. Doing so, the object will be resolved with$term
and$category
properties.