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
Use the OverlayToaster component in a React 18 application.
Observe the console warnings about ReactDOM.render() being deprecated.
Actual behavior
The OverlayToaster component in BlueprintJS uses the ReactDOM.render() method, which is deprecated in React 18. This causes the application to behave as if it's running React 17, according to the warning message from React.
Expected behavior
The OverlayToaster component should use the new ReactDOM.createRoot() method introduced in React 18, so that it can take advantage of the new features and improvements in React 18.
Possible solution
Update the OverlayToaster component to use ReactDOM.createRoot() instead of ReactDOM.render(). This might involve refactoring the component to accommodate the new root API, which involves creating a root and then calling render on it, as opposed to the legacy API where render is called directly with the component and container.
The text was updated successfully, but these errors were encountered:
Environment
Steps to reproduce
Use the OverlayToaster component in a React 18 application.
Observe the console warnings about ReactDOM.render() being deprecated.
Actual behavior
The OverlayToaster component in BlueprintJS uses the ReactDOM.render() method, which is deprecated in React 18. This causes the application to behave as if it's running React 17, according to the warning message from React.
Expected behavior
The OverlayToaster component should use the new ReactDOM.createRoot() method introduced in React 18, so that it can take advantage of the new features and improvements in React 18.
Possible solution
Update the OverlayToaster component to use ReactDOM.createRoot() instead of ReactDOM.render(). This might involve refactoring the component to accommodate the new root API, which involves creating a root and then calling render on it, as opposed to the legacy API where render is called directly with the component and container.
The text was updated successfully, but these errors were encountered: