Skip to content

fix(#44): guard set_progress_contract against double-call, add update…#208

Open
knytcomics-ui wants to merge 1 commit into
scout-off:mainfrom
knytcomics-ui:fix/44-set-progress-contract-guard
Open

fix(#44): guard set_progress_contract against double-call, add update…#208
knytcomics-ui wants to merge 1 commit into
scout-off:mainfrom
knytcomics-ui:fix/44-set-progress-contract-guard

Conversation

@knytcomics-ui
Copy link
Copy Markdown

…_progress_contract

  • Add AlreadyConfigured = 11 to VerificationError
  • Add ProgressContractSet DataKey flag
  • set_progress_contract returns AlreadyConfigured on second call
  • Add update_progress_contract for intentional re-wiring (emits progress_contract_updated event)
  • Add unit tests for both paths

closes #44

…dd update_progress_contract

- Add AlreadyConfigured = 11 to VerificationError
- Add ProgressContractSet DataKey flag
- set_progress_contract returns AlreadyConfigured on second call
- Add update_progress_contract for intentional re-wiring (emits progress_contract_updated event)
- Add unit tests for both paths
@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented May 31, 2026

@knytcomics-ui Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

set_progress_contract has no guard against being called twice

1 participant