feat: Use RepoType in Repo and impl DefaultStorage #414
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.
RepoType
trait inRepo
DefaultStorage
to mimic previous implementation for default handling of storageEither
andArc
implementation against the data and block store traits.set_namespace
to allow one to define the namespace for indexeddb during the initialization process.set_storage_type
(will be replaced byRepoType
in the future)async-trait
fromBlockStore
,DataStore
, andPinStore
, using RPiT in its place to returnimpl Future
.Note:
RepoType
back intoRepo
to remove the need of dynamic dispatch when storing the storage handler inRepo
, which should help to reduce allocation and footprint.DefaultStorage
is currently defined as the default backend for handling memory, file, and web (via indexeddb) storageIpfs
will eventually be structured asIpfs<S: RepoType>
to eventually support custom storage backends in the future, with a prelude that would useDefaultStorage