CPLAT-5909 Update error boundary component to use the init method

[joebingham-wk]

Motivation

The init lifecycle method was introduced in part to allow for set to be state prior to component mounting. With the current code generation script, the typing conflicts because the generated code expects a JsBackedMap while react-dart accepts any Map. This results in a runtime error.

Changes

• Modify the generation script to cast the passed in Map to a JsBackedMap.
• Update the stateful component test to use the init method to ensure it behaves the same as getInitialState.
• Replace getInitialState with init within error_boundary_mixins.dart.

Release Notes

Review

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

Please review:
@aaronlademann-wf @greglittlefield-wf @kealjones-wk

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:
    • Pull this branch down
    • Run webdev serve web
    • Verify the error boundary component works while using the init() lifecycle method.
  • 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 Client Platform 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]

Can we make this message for helpful to the consumer by instructing them to use the initializeState method instead?

[joebingham-wk]

Yep, good call. Because it's the general state setter I updated the message to also mention setState. Let me know if the new message could be improved as well!

[aaronlademann-wf]

@joebingham-wk this is looking good, but the build is failing.

This is because your changes are dependent on Workiva/react-dart#187, but the dependency override has not been updated to reflect that in pubspec.yaml.

You were correct to point out the dependency in your PR description, and to place the Hold label. However, when working on PRs / branches that depend on one another, you should also go ahead and add/update the dependency override within pubspec.yaml so that we can verify that the build will pass using the changes that are external to this lib.

dependency_overrides:
  react:
    git:
      url: https://github.com/cleandart/react-dart.git
-      ref: 5.1.0-wip
+      ref: CPLAT-5908-Add-initializeState

Then, once the CPLAT-5908-Add-initializeState branch merges into react-dart 5.1.0-wip, you can switch it back to 5.1.0-wip. If the PR was not going into an integration branch like this one is, you would just remove the dependency override altogether at that time.

[joebingham-wk]

Awesome, that explanation helps a lot. Thank you!

[aaronlademann-wf]

+1

[aaronlademann-wf]

+10

@Workiva/release-management-pp