You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phase 1: Upgrade React packages to version 18 and keep running in Legacy mode, which should behave mostly similarly to React@17.
Phase 2: Gradually migrate to Concurrent mode.
We’re almost ready to complete phase 1:
All types breaking changes have been addressed and Kibana is already using @types/react@18 in main
We’re finishing fixing unit tests and breaking changes. Kibana is already using the latest @testing-library/react in main and we’re finalizing the breaking changes that are backward compatible and can be merged separately.
We’ve addressed all runtime issues found by functional tests and CI functional tests are now green when running with React@18.
Kibana’s UI functional tests coverage and a very small number of discovered runtime issues give us a lot of confidence, but we would like to ask teams to help with manually testing their UIs to try to discover any UI issues that could have been missed by functional testing.
The purpose of this meta issue is to track any runtime issues caused by an upgrade to React@18 in Legacy Mode.
Shared UX team is working on React@18 upgrade.
We plan to upgrade in 2 phases:
We’re almost ready to complete phase 1:
Kibana’s UI functional tests coverage and a very small number of discovered runtime issues give us a lot of confidence, but we would like to ask teams to help with manually testing their UIs to try to discover any UI issues that could have been missed by functional testing.
The purpose of this meta issue is to track any runtime issues caused by an upgrade to React@18 in Legacy Mode.
Runtime issues discovered by functional tests
useId
can't be used withquerySelector
.value
of controlled text input inuseEffect
is causes typing issuesuseLayoutEffect
insearch_box
eui#8047useLayoutEffect
when setting value from a prop inreact-monaco-editor
#195775useEffect
must return undefined or destroy function, objects no longer alloweduseEffect
return value #195421Issues discovered outside of functional tests
... Please add any issues that are found outside of functional tests ...
The text was updated successfully, but these errors were encountered: