-
Notifications
You must be signed in to change notification settings - Fork 226
docs: explain versioning guarantees and format evolution #9947
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
Changes from all commits
008b357
4704bf5
9b627a8
de0576e
713e3a7
574925c
1176d86
4935ecf
ca8cfad
3b410bb
0ac688c
1f81692
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
connortsui20 marked this conversation as resolved.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this diagram is a bit misrepresentative and the bottom text is irrelevant
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would be better to have something that differentiates original encoding to revved encoding. Vertical partition in diagram maybe. Something like DBP array (1 child, doesn't support 128 and 256) <- serde -> decimal_byte_parts serialized DBP array (1 - 4 children, supports 128 and 256) <- serde -> decimal_byte_parts serialized (v1) OR decimal_byte_parts serialized (v2) |
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.
can we not make this from a markdown system?
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 think its a bit hard, and not sure what is wrong with an svg