-
Type: Investigation
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
None
-
Not Needed
-
Iteration Jellyfish, Iteration Kraken
The cloud frontend is going to be on react 17 by the end of the quarter. Our components are currently causing issues and blocking the upgrade.
While we may want to consider addressing directly those specific issues and allow the shared component to work with both react 16 and 17 it may be good to attempt a full update on our side to get a sense of the effort.
If possible we want to stay aligned to the Cloud version of react and remove friction and unknowns during the integration.
Goals of the investigation:
- Attempt a full update to react 17
- Assess the effort to complete the update and fix any issue
- Assess the effort to only directly address issues affecting Cloud:
- compass-aggregations - entire plugin
- compass-crud - document view, insert document dialogue
- compass-export-to-language - entire plugin
- compass-query-bar - entire plugin
- Create follow-up tickets
Timebox: 5 days
- is related to
-
COMPASS-6133 Remove usage of Modal component from react-bootstrap
- Closed
-
COMPASS-6134 Remove usage of Dropdown component from react-bootstrap
- Closed
-
COMPASS-6135 Remove usage of react-select-plus component
- Closed
-
COMPASS-6136 Remove usage of a string ref in chart-component component
- Closed
-
COMPASS-6137 Refactor usage of UNSAFE_ methods in document-table
- Closed
-
COMPASS-6138 Refactor usage of UNSAFE_ methods in cell-editor
- Closed
-
COMPASS-6139 Refactor usage of UNSAFE_ methods in insert-document-dialog
- Closed
-
COMPASS-6140 Replace usage of react-sortable-hoc with @dndkit
- Closed
-
COMPASS-6141 Update redux / react-redux to latest
- Closed
-
COMPASS-6142 Update react, react-dom to 17
- Closed
-
COMPASS-6143 Wrap React root render in React.StrictMode component
- Closed