Problem is that the SearchField component was using this.props.<function> as onClick events rather than the "wrappers" in this.<function>, resulting in the event object being passed as the first argument to functions in the container, and thus unexpected behavior.
The fix is to use the component's wrapper functions instead, as was initially intended.
Issue #66
Problem is that the
SearchFieldcomponent was usingthis.props.<function>asonClickevents rather than the "wrappers" inthis.<function>, resulting in theeventobject being passed as the first argument to functions in the container, and thus unexpected behavior.The fix is to use the component's wrapper functions instead, as was initially intended.