store: burn_after_reads>0 implies burn-after-read (#82) #107

Merged
fen merged 1 commits from fix-82-burn-implies-budget into dev 2026-09-09 23:40:22 +00:00
Owner

Fixes #82

  • internal/store/store.go: resolve readsLimit whenever BurnAfterRead is true OR BurnAfterReads != nil && > 0; burn_after_reads > 0 alone now sets BurnAfterRead so a POST with only {"burn_after_reads":N} creates a burning paste instead of an immortal one.
  • internal/api/burnreads_test.go: TestBurnReadsImpliedByBurnAfterReads covers burn_after_reads-only (burns after N reads); existing burn_after_read+burn_after_reads tests unchanged and passing.

go vet ./... and go test ./... pass.

Fixes #82 - internal/store/store.go: resolve readsLimit whenever BurnAfterRead is true OR BurnAfterReads != nil && > 0; burn_after_reads > 0 alone now sets BurnAfterRead so a POST with only {"burn_after_reads":N} creates a burning paste instead of an immortal one. - internal/api/burnreads_test.go: TestBurnReadsImpliedByBurnAfterReads covers burn_after_reads-only (burns after N reads); existing burn_after_read+burn_after_reads tests unchanged and passing. go vet ./... and go test ./... pass.
poslop added 1 commit 2026-09-09 23:28:01 +00:00
store: burn_after_reads>0 implies burn-after-read mode (#82)
CI / docker (pull_request) Skipped
CI / test (pull_request) Successful in 24s
f37cc932c4
fen merged commit 9d89995c91 into dev 2026-09-09 23:40:22 +00:00
Sign in to join this conversation.