[pickers] Add context to onAccept callback

[flaviendelangle]

Closes #11978

Do you think we should add a demo? And if so, where?

[mui-bot]

Deploy preview: https://deploy-preview-13511--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 093e18e

[LukasTy]

Great addition! 🙏
Thank you for taking care of it. 👍

Do you have any idea of what we can showcase with it?
Currently it seems that this addition will allow preventing srange behaviors if users are relying on onAccept for certain triggers. 🤔
But if you have ideas for documentation—"I'm all ears". 👍

[flaviendelangle]

Do you have any idea of what we can showcase with it?

I think the context param is never really documented even for onChange, which probably limits a lot the amount of people using it.

Maybe we could rename the sections in Pickers lifecycle to be onChange / onAccept / onClose.
And then in onChange and onAccept we have a sub-section "When is is `onChange called" and a sub-section "Usage" or something like that.

[LukasTy]

I think the context param is never really documented even for onChange, which probably limits a lot the amount of people using it.

I do agree, we could improve on that. 👍

Maybe we could rename the sections in Pickers lifecycle to be onChange / onAccept / onClose.
And then in onChange and onAccept we have a sub-section "When is is `onChange called" and a sub-section "Usage" or something like that.

Given your suggestion, it seems that this idea is out of the scope of this issue/PR. 🤔

[flaviendelangle]

Given your suggestion, it seems that this idea is out of the scope of this issue/PR.

Yes, I can do it in a follow up