feat: add cron-style history pruning policy with admin controls - #297
Open
Elizabeth-dev270 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #94
I’m examining the existing pruning logic and test layout first so I can wire the new policy cleanly and verify it with focused regression tests.
No matches found. Your search pattern might be excluded completely by either the search.exclude settings or .*ignore files.
If you believe that it should have results, you can check into the .ignore files and the exclude setting (here are some excluded patterns for reference:[/node_modules,/bower_components,**/.code-search]).
Then if you want to include those files you can call the tool again by setting "includeIgnoredFiles" to true.
I’ve located the existing retention entry points and am reading the surrounding contract state to make the new policy consistent with the current authorization and event model.
I'm adding a small regression test that exercises the intended admin API and storage shape before wiring the implementation, so the failure mode is explicit and reproducible.
Replacing 10 lines with 76 lines in
The new regression coverage is in place; I’m running the targeted Rust tests now to confirm the exact compile/runtime gaps the contract needs to close.
Ran terminal command: cd /workspaces/ApexChainx-Contracts && cargo test -p apexchainx_calculator test_set_and_get_prune_policy_round_trips -- --nocapture
Made changes.