Avoid accessing private members of child modules

[dustyholmes-wf]

Motivation

In dart 2.19 mocks can no longer handle calls into these private members.

Changes

Wrap calls into _parentContext in a try...catch to handle this gracefully.

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:
  • 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 Architecture 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

[aviary2-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.

[robbecker-wf]

It might be good to add a comment inside the {} saying that swallowing the exception and not logging or acting on it is intentional so someone doesn't come along later and remove this try catch thinking that it doesn't do anything.

[robbecker-wf]

+10 @Workiva/release-management-p

[rmconsole-wf]

+1 from RM