-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DatePicker: utilize custom onChange handler when provided #10424
DatePicker: utilize custom onChange handler when provided #10424
Conversation
Asset size changes
Baseline commit: 72e835bd59d6c29b1a222fccdd5c57a339c73090 (build) |
Component Perf AnalysisNo significant results to display. All results
|
@lorejoh12 will be back starting tomorrow so hopefully he can take a look once settled at work :) |
Hello @KevinTCoughlin! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
🎉 Handy links: |
🎉 Handy links: |
Pull request checklist
$ yarn change
Description of changes
These changes integrate the optional custom
onChange
handler within the existing defaultonChange
handler.Now, a user can pass in their own
onChange
handler to thetextField
prop of DatePicker and see theironChange
called.I made these changes both to the
date-time
package and theoffice-ui-fabric-react
package. Let me know if these changes should just go in one.Focus areas to test
Ensure that a custom
onChange
handler is called in addition to the existing defaultonChange
handler.I added a test for this scenario, too.
Microsoft Reviewers: Open in CodeFlow