[DCJ-179] Completely remove react-hyperscript-helpers
#2595
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.
Addresses
https://broadworkbench.atlassian.net/browse/DCJ-179
Summary
Now that #2582 has gone in, we can completely remove
react-hyperscript-helpers
.Background
This is the final piece of a conversion process that began in November of 2023.
The DUOS (now Data Custodian Journeys, or DCJ) team has been participating in the Terra UI working group meetings and aligning the DUOS UI codebase with Terra UI best practices where feasible. One of the decision taken by the working group was to migrate away from
react-hyperscript-helpers
to using regular JSX.The pros and cons of
react-hyperscript-helpers
have been vigorously debated in the Terra UI working group meetings, but in short the main cons were that the library has not been updated since 2018 and it is a relatively niche library, whereas React examples assume use of JSX or TSX.For the DCJ team, this is especially important since we are a smaller team and have a lot of co-ops with React and JSX experience but not
react-hyperscript-helpers
experience, so this increases onramp time. The removal of outdated libraries from our UI is also important to lower our complexity, dependency churn, and our security upkeep burden.Acknowledgements
A huge thanks to all the teammates who participated in migrating over these components to JSX, especially @PintoGideon who converted some of our largest and most challenging components.
Statistics
By the numbers, this represents:
Have you read Terra's Contributing Guide lately? If not, do that first.