-
Notifications
You must be signed in to change notification settings - Fork 30
Move manifest list reader from spec crate #48
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
Conversation
222049e
to
53d78f9
Compare
I wonder if moving the manifest file reader out of the Let me know what you think. |
It's nice to have the |
And there is the question about the naming scheme. So far I've called the reader of the manifest list "ManifestListReader" and the reader of the manifest "ManifestReader". If you would like to rename "ManifestReader" to "ManifestFileReader", it kind of breaks the naming scheme. |
Right, I forgot to rename some variables here and there ( |
After a discussion on the naming convention, we agreed that it's better to stick with Manifest for manifest files and ManifestList for manifest list files. |
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.
Looks good to me. Thanks for taking this on
The manifest list reader should be in the same crate as the manifest file reader (main iceberg-rust).