refactor(api): dispatchInputs struct in DispatchAction (#165)#205
Conversation
Closes #165 (audit F032 + F048). Groups the five loose locals DispatchAction extracted from either ActionSource branch (actionType, desiredState, params, timeoutSeconds, actionID) into a single dispatchInputs struct. Downstream sites (eventData / sign / taskqueue payload / log) now read from inputs.X — the "where did this value come from" question has one answer. The struct's field comments document each value's source-branch provenance (stored vs inline), folding F032's "var params any" clarification into the right home — the field comment instead of a free-floating inline comment that travels with neither caller. signature + paramsCanonical stay separate per the acceptance criteria — they're computed downstream by the re-sign step, not extracted from either branch. No behaviour change; all DispatchAction tests stay green (~80s incl. testcontainer setup).
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesInput Consolidation Refactor
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Summary
Closes #165 (audit F032 + F048).
Groups the five loose locals `DispatchAction` extracted from
either ActionSource branch (`actionType`, `desiredState`,
`params`, `timeoutSeconds`, `actionID`) into a single
`dispatchInputs` struct. Downstream sites (eventData / sign /
taskqueue payload / log) now read from `inputs.X` — the "where
did this value come from" question has one answer.
The struct's field comments document each value's source-branch
provenance (stored vs inline), folding F032's `var params any`
clarification into the right home — the field comment instead of
a free-floating inline comment that travels with neither caller.
`signature` + `paramsCanonical` stay separate per the acceptance
criteria — they're computed downstream by the re-sign step, not
extracted from either branch.
No behaviour change; all DispatchAction tests stay green (~80s
incl. testcontainer setup).
Test plan
Summary by CodeRabbit