This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
Moves accounts-db test-only code into a dev-context-only-utils feature #32718
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.
Problem
To prepare for splitting the runtime crate, we'll need access to some private/test-only functions from accounts-db. To simplify that move, we can consolidate the test-only code within accounts-db into
dev-context-only-utils
feature blocks.Summary of Changes
Moves all the test-only code into dev-context-only-utils feature blocks, and update the callers.
Refer to #32169 for more information about
dev-context-only-utils
.Note, this diff is large. No actual implementations changed. There is a lot of moving code. There is some changing private to public (but only public within a test-only feature).