You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering a situation where using reflect to bind a function with multiple arguments only seems to pass the first argument. I'd like to clarify if this is the intended behaviour.
Reflect functionality based on scopeBind, which initially was created for binding events and effects, and as they could only have one argument this feature was also applied to scopeBind with function too. There is no reason to keep this restriction on plain function, so we can remove it. Thanks for report, we overlooked this case!
Probably will be added in next minor or major effector release
Description
I'm encountering a situation where using
reflect
to bind a function with multiple arguments only seems to pass the first argument. I'd like to clarify if this is the intended behaviour.Current Implementation
Current Behaviour
When calling the bound function with multiple arguments, only the first argument is received:
Additional Context
Question
Is this the expected behavior for binding functions with multiple arguments?
Any clarification would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: