Reactor: Decoupling pool-registry from pool-system and pool-fees #1983
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.
Description
The intention of this PR is to clean the mess we currently have when testing/benchmarking pool things from pool-registry PoV. Almost no production logic is touched, only for cases that affect the benchmarking
NOTE: Current tests do not cover everything, but they cover what the same they covered before the refactor.
Changes and Descriptions
pool-registry
(look at themock.rs
file!)BoundedVec
when needed to carry the Max information associated to those vecsPoolMetadata
trait which is not used.Still WIP
execute_update
benchmark