feature/APPEALS-43728-react-upgrade-18 #1722
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves APPEALS-44522
Description
The following details the changes made to upgrade eFolder to React 18.2.0. The changes made involve necessary syntax updates, complaint versioning, and addressing breaking changes, all of which are made to resolve warnings received during the upgrade process.
React and React-DOM Versions:
React-Router-DOM Version:
*Note - React Router is necessary to upgrade to be compliant with the React 18 which deprecates childContextTypes API which is no longer supported and will be removed in the next major release.
The upgrade is made to v5 to be consistent with Caseflow Frontend Toolkit.
Caseflow Frontend Toolkit:
*Note - the above upgrade to the Caseflow Frontend toolkit is a test branch that points to upgrades necessary for the toolkits compliance with both Caseflow and eFolder. The toolkit itself also requires updates to React 18.2.0. As far as eFolder is concerned the update only includes a change for the Redux Base component which wraps the root and passes the redux store. Caseflow Frontend toolkit upgrade branch
Refactoring of index.jsx