Skip to content

fix: clear read count when burn after read is checked#118

Open
mvanhorn wants to merge 1 commit intoosbytes:mainfrom
mvanhorn:fix/burn-after-read-unsets-read-count
Open

fix: clear read count when burn after read is checked#118
mvanhorn wants to merge 1 commit intoosbytes:mainfrom
mvanhorn:fix/burn-after-read-unsets-read-count

Conversation

@mvanhorn
Copy link
Copy Markdown

Summary

  • When "burn after read" is checked, the read count value is cleared to undefined
  • Mirrors the existing inverse behavior at line 864 where setting a read count unchecks burn after read
  • These two options are mutually exclusive; now both directions auto-clear the other

Closes #103

Test plan

  • Check "burn after read" after setting a read count value: read count should be cleared
  • Set a read count value: burn after read should still auto-uncheck (existing behavior unchanged)
  • Uncheck "burn after read": read count field should remain empty (no regression)

When the burn after read checkbox is checked, the read count
input is now cleared to undefined. This matches the existing
inverse behavior where setting a read count unchecks burn
after read, since these options are mutually exclusive.

Closes osbytes#103
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.

Selecting 'burn after read' should unset 'read count'

1 participant