FED-471 Add utilities for jsifying/unsifying context props

[greglittlefield-wf]

Motivation

Some JS components accept a custom React Context as a prop, and we want to support interop-ing with those components in a consumer-friendly way.

In react-dart/over_react, APIs that deal with React context, like createContext and useContext, use a Dart wrapper around the JS React context object.

So, consumers are dealing with Dart context, while JS components need JS context. Ideally, consumers shouldn't have to manually wrap/unwrap context when they're passing it to/from JS components.

Changes

• Add unjsifyContextProp/jsifyContextProp utility methods, similar to the ones for refs and maps
• Add test cases
• Update JS interop documentation

Release Notes

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:
    • Tests pass
  • 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

AWESOME!

[aaronlademann-wf]

+10

• Tested in unified using the analogous RMUI branch, everything context related works as expected.

@Workiva/release-management-pp

[rmconsole-wf]

+1 from RM