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.
Based on the React 18 Upgrade Guide, I made some minor changes to the
index.js
andApp.js
files to render the React app itself. But the biggest change is that React now recommends defining components as functions instead of classes. This involved addinguseState()
state variables, converting lifecycle hooks touseEffect()
functions, and destructuring props.While I tried to maintain the vast majority of the functionality in every component, there are a few issues (like the reports not rendering properly). I figure that this isn't a real cause for concern, since most of these components will likely be rewritten in the next few months based on the new UX.