Skip to content

Latest commit

 

History

History
31 lines (22 loc) · 1.37 KB

File metadata and controls

31 lines (22 loc) · 1.37 KB

Contracts Contributor Checklist

Use this checklist before opening a contracts PR.

Environment

Validation

  • Run focused tests for every contract you changed.
  • Build every changed contract for wasm32-unknown-unknown --release.
  • Run cargo clippy -- -D warnings in every changed contract directory.
  • Run cargo fmt -- --check in every changed contract directory.
  • If a change spans multiple contracts or shared crates, run the CI-parity sweep from TESTING.md.

Behavior checks

  • Add or update tests for new storage, auth, and ledger-timing behavior.
  • Prefer explicit assertions for balances, events, and status transitions.
  • Use snapshot-style assertions only when serialized payloads are large or repetitive and the output shape is intentionally stable.
  • Update any contributor-facing docs when commands or workflows change.

Before review

  • Confirm new docs link back to the docs index when they are meant to be entry points.
  • Keep contract-specific command examples aligned with TESTING.md.
  • Include the exact validation commands you ran in the PR description.