Document iteration function code structure we intend to use #2867
Labels
docs
Improvements or additions to documentation
type: refactor
Architecture, code or CI improvements that may or may not tackle technical debt.
Summary
Document the format we intend to have for our keeper iteration functions which allows for optmization and reuse outside of the keeper.
The format decided on was implemented for
IterateClientStates
in this pr. See the top comment:The idea is that for every key path we store, there should be an associated iteration function. This function should take in a prefix and a callback. It should begin iteration at the top level of the store. It should parse any necessary information from the key and value and then perform a callback (given a provided function by the caller). This will allow for optimized iteration in a generic enough format that the caller can perform specific iteration (such as iterating over a client type) without adding an additional function into the keeper
Each function should look similar to:
For Admin Use
The text was updated successfully, but these errors were encountered: