-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(db): move reth-db-api::encode and decode to reth-db-serialization #10822
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, this separates the trait from the db-api
I think this makes sense, wdyt @joshieDo
although the encode/decode traits are specifically intended for database, but since the crate is named codec this seems like an appropriate location I think
Imo, I don't think they should move to codecs. They're inherently db-traits which can be fulfilled by codec(s). maybe another crate db-serialization or smth like that? |
I see this |
reth-codecs in my view is for actual codecs and their impl. these traits do not implement any codec. they are database specific traits. |
42cb18b
to
c88195c
Compare
add crate db-serialization as your suggestion. PTAL @joshieDo |
7376f1d
to
1fd6735
Compare
@mattsse ping. PTAL |
move shared_key, account, storage_shared_key to reth-db-models add mod encode, decode add crate reth-db-serialization
Closes #10821. ref #10081 .
follow up move compress to reth-db-serialization