AF-2888 Accommodate tracing of Store triggers and resulting redraws

[greglittlefield-wf]

Ultimate Problem

To implement tracing of Flux components in https://github.com/Workiva/app_intelligence_dart/pull/737, we needed a way to:

• know whether a call to redraw was triggered from a store handler, and know which store triggered the redraw
• set up a custom default handler for certain types of stores

Solution

• Add lifecycle methods to allow subclasses to safely hook into and override store redraw logic:
  • listenToStoreForRedraw
    • See example override here
  • handleRedrawOn
    • See exampleoverride here
• Add Tests

Testing

• Verify tests pass
• Smoke test examples

---

@dustinlessard-wf @kealjones-wk @evanweible-wf
@aaronlademann-wf @kealjones-wk

[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 HipChat: InfoSec Forum.

[greglittlefield-wf]

This was needed to get a passing build now that Dart 2 is stable

[kealjones-wk]

QA +1

• Testing instruction
• Dev +1's
• Dev/QA +10 with detail of what was tested
  • Verify tests pass
  • Smoke test examples
• Unit tests created/updated
• All unit tests pass
• Rosie has run and reports properly the release the ticket will be included in

Merging into master.

[kealjones-wk]

@Workiva/release-management-pp