FED-1729 Prepare for react-dart 7.0.0

[greglittlefield-wf]

Motivation

The not-yet-released react-dart 7.0.0 contains breaking changes that will need to be addressed in over_react before it's compatible.

We'll be making these compatibility changes proactively in order to make testing of the WIP react-dart 7.0.0 branch easier, and also to validate that we won't hit any blockers that require tweaks to the major changes in react-dart 7.0.0.

This PR won't be raising the upper bound of over_react's react-dart dependency, but once react-dart 7.0.0 is released, there shouldn't be any additional code changes necessary to raise that upper bound.

Changes

• Update usage of deprecated react.main to use react.htmlMain
• Add internal copy of react-dart's forwardRef, removed from react-dart 7.0.0 but still used by over_react's forwardRef
  • over_react's forwardRef is deprecated, and will be removed in the next major, along with this copy
• Remove tests that rely on jsThis being null in unmounted components
  • This is in response to behavior changes in react-dart 7.0.0 to throw instead of returning null.
  • Since we didn't ever need to support unmounted components in the first place (the tested utility is only used internally on mounted components), we'll just remove the tests.
• Reuse jsifyPropTypes super logic to avoid reimplementing JS interop
  • This eliminates JS interop logic that was duplicated from react-dart, which relied on APIs removed in react-dart 7.0.0, and in general was at risk of getting out of sync.
  • These changes were backported from the null-safety branch.
• Add useRefInit that just forwards to react-dart's useRefInit, update analyzer plugin

Release Notes

• Update internals to prepare for react-dart 7.0.0

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Frontend Frameworks Design member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[aaronlademann-wf]

+1

+10 (passing CI)

[aaronlademann-wf]

🏅

[greglittlefield-wf]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM