feat(storage): make snapshots non-optional in provider factory #6344
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.
Snapshots are becoming the integral part of querying any data from Reth node (from both inside our codebase and outside using the external process DB access): we store headers, transactions and receipts in snapshots, and want to make the way users access data abstracted away from the notion of MDBX/static file storage.
This PR makes
SnapshotProvider
inProviderFactory
non-optional, meaning that to initialize a provider factory you'll need to specify a path to the snapshots directory.