onChange of <Input> no longer pass event object

Hi,

We use Quantum in some projects here @catho-lab and recently I've upgraded our quantum package to the latest version and started to experience some strange behaviors.

Troubleshooting the problem it turned out that the culprit was one change of behavior at the onChange event at component. The onChange event no longer sends back the event object, nor the changes.

onChange call at my previous version:

quantum/components/Input/Input.jsx

Line 152 in 9a6e8b8

onChange(e, { value });

onChange call at master:

quantum/components/Input/Input.jsx

Line 109 in debce31

onChange();

Is this intentional?

Right now I'm rolling back to the last version that had this event return pattern, but it's definitely not ideal since I'll be losing all the bug-fixes and improvements of the recent versions.

Thanks.

~~If this isn't an intentional behavior, I've added #135 to address it.~~
Edit: Candidate fix now lays at #136 by @pedrohmorais;

🎉 This issue has been resolved in version 2.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀