onChange does not follow the normal event handling design pattern

[FoxyWolfy]

Tech	Version
@material-ui/pickers	v3.2.8

onChange does not follow normal event handling design pattern. Please provide the original DOM event to onChange.

o Always provide the event as the first argument to any user facing event prop handler
o The "event.target" needs to be supplied
o The "event.target.name" should be the control name
o The "event.target.value" should contain the "date"

What's not obvious is where the date originated from. Without the event a complex app doesn't have the originating "event.target" and therefore cannot determine the originating control with "event.target.name".

All we get is a "date". From which control? We have multiple modules with dozens of controls that send changes up to a parent. This is the only control that doesn't forward the event on an onChange.

We cannot use material-ui-pickers until onChange supports the established event handling design pattern

[dmtrKovalenko]

Duplicate of tons of issues

[FoxyWolfy]

Aren't you suppose to link this issue to the duplicate issue?
Just closing issues as you are doing displays extremely poor development methodology.

[dmtrKovalenko]

Only issues that was found super fast, there are more #182, #473, #483, #644, #974. Please try to search through the currently closed issues before opening new one