Ability to use Named parameters in Laravel functions #55728
Replies: 2 comments 4 replies
-
|
Laravel is full of |
Beta Was this translation helpful? Give feedback.
-
|
According to a search, there are only 81 uses of public function tags($names)
{
return new TaggedCache($this, new TagSet($this, is_array($names) ? $names : func_get_args()));
}could be replaced by: public function tags(...$names)
{
return new TaggedCache($this, new TagSet($this, $names));
}If names are not well chosen, then changing them to something that can be stable at the time of making the above changes would solve that. Edit: Actually it might not be quite as simple as this... it would work for public function cleanup_elipsis_parameter(array: $parameter): array
{
if (count($parameter) === 1 && is_array($parameter[0])) {
return $parameter[0];
}
return $parameter;
} |
Beta Was this translation helpful? Give feedback.
-
|
Would be cool if we had an attribute to correctly handle the input Not sure if this would remove the warning from the docs:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I know, it was more meant as a rhetorical question, meaning: As long as this warning exists, the expectation for named parameters to be guaranteed to work is a little pointless
No objection here. I was just opting for clear communication on Laravel's part |
Beta Was this translation helpful? Give feedback.
-
|
@myregistration can you give us a code example of that can function call? |
Beta Was this translation helpful? Give feedback.
-
Please allow us to pass arguments to a function by specifying the parameter name rather than having to rely on the position in the function's parameter list.
For example, I'd like to pass named parameters to the can() gate function, but it doesn't support it.
Beta Was this translation helpful? Give feedback.
All reactions