Description: Investigate FMS behavior under unusual inputs: empty children, null refs, zero duration, very long duration, rapidly toggled visible props, identical motion props passed twice in rapid succession, motion components nested inside themselves. Audit for crashes, infinite loops, console errors, silent corruption. Produce a findings report. Land small fixes (e.g., null-guards, prop validation warnings in dev) in scope; defer larger validation framework work.
Why it matters: Real product code passes weird inputs sometimes — especially when inputs come from server data, from user interactions, or from dynamically-generated UI. Defensive patterns aren't glamorous but they're how a system becomes trustworthy.
- Difficulty: Easy-Medium (mostly mechanical; the audit finds the surprises)
- Sequencing: M3 W11
- Tags:
partner-pickup
Description: Investigate FMS behavior under unusual inputs: empty children, null refs, zero duration, very long duration, rapidly toggled
visibleprops, identical motion props passed twice in rapid succession, motion components nested inside themselves. Audit for crashes, infinite loops, console errors, silent corruption. Produce a findings report. Land small fixes (e.g., null-guards, prop validation warnings in dev) in scope; defer larger validation framework work.Why it matters: Real product code passes weird inputs sometimes — especially when inputs come from server data, from user interactions, or from dynamically-generated UI. Defensive patterns aren't glamorous but they're how a system becomes trustworthy.
partner-pickup