-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Migrate Calendar components to function components #12928
Conversation
Co-Authored-By: Elizabeth Craig <[email protected]>
…ic-react into functional/hooks
Co-Authored-By: Elizabeth Craig <[email protected]>
Co-Authored-By: Elizabeth Craig <[email protected]>
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
@dzearing @ecraig12345 Not sure of the advice concerning this build error:
Basically, since certain types are being re-exported from multiple components, and those types are now technically different when they're from different source files (OUFR vs react-next), we get this error. Should we just copy OUFR over to react-next wholesale? |
@MLoughry Would you mind splitting out the default props utility into a different PR? It will be easier to get that specific part reviewed and merged. @lorejoh12 Could you take a look at the other parts of this? |
The issue with exporting stuff from multiple places is probably something we should fix as part of version 8--apparently it's already causing problems for people in some cases (see #12350). In some cases it will be a bit tricky to determine the single "right" place things should be exported from, but it seems pretty obvious that DatePicker shouldn't be exporting Calendar stuff. So maybe for this specific case, you could change react-next/src/DatePicker to manually export only DatePicker stuff? (copying oufr/src/components/DatePicker/index minus the Calendar line) |
Gentle ping that this issue needs attention. |
@ecraig12345 @joschect Any further concerns blocking sign-off? |
I've started a conversation with the code owners here; not sure about this one. |
Ok after talking with @lorejoh12 , let's do this:
There are numerous issues which have been resolved in date-time, but not in the existing v7 This also applies to DatePicker. Sorry for the trouble @MLoughry! |
Pull request checklist
$ yarn change
Description of changes
Migrate all Calendar components to function components.
Also added a utility method for function components to apply default properties, as a replacement for
static defaultProps
Focus areas to test
(optional)
Microsoft Reviewers: Open in CodeFlow