Refactor ORM QueryBuilder::setParameters()
calls to use setParameter()
instead due to a stricter type in 3.0
#2710
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.
For B/C, the ORM's
QueryBuilder::setParameters()
(plural) method has continued to accept a plain array throughout 2.x, but in 3.0 it is typehinted as anArrayCollection
. So instead of having to pass a collection of Parameter objects, emulating the internals ofsetParameter()
(singular), this just updates the code to call thesetParameter()
method one-by-one (which shouldn't hurt any since these are only 2-item arrays).After #2639 it should be more feasible to see where some of the pain points lie, but for now, another piece of low-hanging fruit is knocked down.