[picker] Disable am/pm for maxTime/minTime, disableTime, and disableFuture props

[A-s-h-o-k]

Changelog

• fixed the bug [pickers] Validation doesn't disable meridiem (AM or PM) for selection #12159

• I have followed (at least) the PR section of the contributing guide.

[A-s-h-o-k]

Hi @flaviendelangle @zannager @LukasTy Could you please review my PR when you have time? I’d love your feedback.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[flaviendelangle]

Thanks for your contribution
I'm currently removing the props passed to all the slots like the toolbar and instead rely on context to help the picker forward information to them.
I plan to add a new context to forward the validation props, I think we need to wait for it before solving this issue 👍

[LukasTy]

I plan to add a new context to forward the validation props, I think we need to wait for it before solving this issue 👍

Do you think it is worth fixing this issue on v7 with a solution similar to what is proposed in this PR? 🤔

[flaviendelangle]

Do you think it is worth fixing this issue on v7 with a solution similar to what is proposed in this PR?

Fixing by adding props then removing then (so a BC), not sure if it the right move

[A-s-h-o-k]

That's a good point about the BC break. Adding props temporarily could solve the issue quickly, but it might not be the best move if the props are removed later.

If the context-based solution will be ready soon, it might make sense to hold off and go straight to that approach to ensure consistency. However, if addressing the issue now is a priority, we could consider adding the props with clear documentation about their temporary nature.

Happy to hear your thoughts and adjust based on the preferred direction! 👍

[LukasTy]

The context-based solution should be available relatively shortly (within 1-2 months). 😉
Just noting that it will only be available on v8, which is currently in the pre-release phase.

[A-s-h-o-k]

Thanks for the update! Given that the context-based solution is coming soon in v8, what do you think our next steps should be for addressing this issue in v7?
Should we proceed with a temporary fix, or focus entirely on the v8 implementation?

[flaviendelangle]

Unless we have a big traction to fix this issue in v7, I would focus solely on the v8 implementation (and make it as good as possible).
If we want to fix it in v7, I would introduce a small context on the time pickers that manually passes those props and consume it in the time picker toolbar. It would not allow custom toolbar to have this behavior but I think it's a decent trade-off.