Skip to content

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

Merged
dillonstreator merged 1 commit intoosbytes:mainfrom
mvanhorn:fix/burn-after-read-unsets-read-count
Apr 27, 2026
Merged

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

Conversation

@mvanhorn
Copy link
Copy Markdown
Contributor

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
@dillonstreator dillonstreator merged commit a2eaa5d into osbytes:main Apr 27, 2026
2 checks passed
adavila0703 added a commit to adavila0703/crypt.fyi that referenced this pull request Apr 30, 2026
Introduces new command-line options for webhook integration during the encryption process. Users can now specify a webhook URL, name, and toggle notifications for various events such as successful reads, failed decryption, and burns. Updated README to include usage examples and detailed descriptions of the new options.

Closes osbytes#118
dillonstreator pushed a commit that referenced this pull request May 1, 2026
* feat: add webhook options for encryption in CLI

Introduces new command-line options for webhook integration during the encryption process. Users can now specify a webhook URL, name, and toggle notifications for various events such as successful reads, failed decryption, and burns. Updated README to include usage examples and detailed descriptions of the new options.

Closes #118

* refactor(cli): collapse webhook flags into --wh-events list and validate via schema

Reworks the CLI webhook interface based on PR review feedback:

- Replace 5 per-event boolean flags with single --wh-events comma-separated list

- Use vaultValueSchema from @crypt.fyi/core for validation instead of manual checks

- Add parseWhEvents and trimmedWhName helpers in new webhook.ts module

- Add jest + ts-jest and unit tests for webhook event parsing

- Update README with new --wh-url, --wh-events, --wh-name usage examples
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'

2 participants