Duplicate state-reset logic in statusCheck catch vs onExited (minor maintainability) #31
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Both the
catchblock (JSON parse failure) and theonExited(code !== 0)handler instatusCheckperform the same four property resets:peers = []ip = ""exitNode = ""binaryAvailable = falseThe logic is duplicated instead of being extracted to a single helper.
Impact
Minor maintainability issue. Any future change to the reset behavior must be made in two places.
Removed duplicate state-reset logic; single reset in onExited. Merged to vibes.
Resolved via merge
daab237. The plugin is confirmed working by @jtmorris. Human code review required before merging to testing.