Skip to content

Conversation

@coreyphillips
Copy link
Collaborator

This PR:

  • Adds activity_wipe_all() to clear all activities and tags
  • Adds blocktank_remove_all_orders() to clear order history
  • Adds blocktank_remove_all_cjit_entries() to clear CJIT entries
  • Adds blocktank_wipe_all() to clear all blocktank tables
  • Adds wipe_all_databases() for global database reset
  • Updates tests and docs as needed

- Add activity_wipe_all() to clear all activities and tags
- Add blocktank_remove_all_orders() to clear order history
- Add blocktank_remove_all_cjit_entries() to clear CJIT entries
- Add blocktank_wipe_all() to clear all blocktank tables
- Add wipe_all_databases() for global database reset
- Update tests accordingly
@coreyphillips coreyphillips requested a review from pwltr October 17, 2025 16:01
@coreyphillips coreyphillips self-assigned this Oct 17, 2025
@ovitrif
Copy link
Collaborator

ovitrif commented Oct 27, 2025

@coreyphillips Can we add @ben-kaufman as reviewer too?
TY

Copy link
Collaborator

@ben-kaufman ben-kaufman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't go over the tests updates yet, but just sharing a few very small comments meanwhile.

Also can you please just explain the rationale/ reason behind adding this wiping option?

@ovitrif
Copy link
Collaborator

ovitrif commented Oct 28, 2025

Also can you please just explain the rationale/ reason behind adding this wiping option?

I can answer this, but since it surfaces an issue I want us to get better at, I will also make my case on it:

As our team is growing, keeping everyone in sync on their topics of interests gets harder; one of the best ways to address this is to adopt async communication. This is rather simple to adopt and has been proven to work magic at many remote-first companies with years of experience: prefer written communication in public spaces.


With that being said, the rationale behind adding the wipe option is to give the mobile native apps the freedom to programmatically control the file storage managed by bitkit core.

- Add get_activity_db() helper to reduce code duplication
- Ensure wipe_all_databases() requires initialized DBs
- Remove unused methods: remove_all_tags(), remove_all_info()
- Consolidate remove_all() into wipe_all() to remove the wrapper
- Document that enum state tables persist across wipes
Copy link
Collaborator

@ben-kaufman ben-kaufman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@pwltr pwltr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't tested but looks good

- Updates bindings
- Bumps version to 0.1.20
@coreyphillips coreyphillips merged commit 1e23b32 into master Oct 29, 2025
@coreyphillips coreyphillips deleted the feat/add-database-wipe-methods branch October 29, 2025 17:37
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.

5 participants