Allow static members in concrete props/state classes

[greglittlefield-wf]

Motivation

It's currently an error to declare members within the body of a props/state class, since the generated class only implements it, not extends it.

However, that error should only apply to instance members, and it currently errors for static members.

Changes

• Allow static members in concrete props/state classes
• Add regression test

Release Notes

• Allow static members in concrete props/state classes in new, mixin-based boilerplate

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

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

[aaronlademann-wf]

+1

[aaronlademann-wf]

+1

[joebingham-wk]

QA +1

[joebingham-wk]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM