Resolving Issue With Named Parameters and Dispatcher#16694
Resolving Issue With Named Parameters and Dispatcher#16694niden merged 1 commit intophalcon:5.0.xfrom
Conversation
b6b7aed to
0a3dc09
Compare
|
@Fenikkusu I will look at this a bit later on. Can you please rebase to target the 5.0.0 branch? We don't merge to master other than releases. Thanks |
a9656a9 to
224eba8
Compare
I was wondering about that. Since it was 5.8.0, I didn't see a compatible branch, hence I went with master. I've updated it to 5.0.x. |
|
...And Now I've got to do a full rebase...fudge... |
78c1154 to
7b2dceb
Compare
|
@Fenikkusu don't worry about the PHP 8.4 build failing (from PECL). That is what we are working on now. |
|
I mean leave the header files as they are. If your PR only fails on PHP 8.4 build then it is good enough. |
46b3ad5 to
46b519c
Compare
I've reverted them out. I get anal about making sure all the testing is passing. |
b94fd55 to
3bd99a6
Compare
27322c0 to
cbc5960
Compare
Side Thought: I normally use Route Converters to Convert IDs to Models. One downside of doing it this way is that you cannot throw proper errors and have them redirected as you can with traditional dispatcher events. In theory, someone could use the new events to do this instead of using Converters. |
cbc5960 to
df7a770
Compare
Updating Changelog Adding Unit Test
df7a770 to
8bee72a
Compare
|
Thank you @Fenikkusu |
Hello!
In raising this pull request, I confirm the following:
Small description of change:
Since PHP 8.0,
call_user_func_arraynow uses arrays with non-numeric keys as named parameters. If you have an action that does not use/define properties, this causes the errorUnknown named parameter. While this can be avoided by adding the parameters, this change fixes it so this is no longer an issue. It also adds in the ability to hook into an event for the calling of the handler, though that was originally just confirmation of the bug. Just making the change to callarray_valuesis enough otherwise.Thanks