-
Notifications
You must be signed in to change notification settings - Fork 12
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
Extension Parameterisation (for comment, DO NOT merge!) #3
Conversation
* Update README.md to include parameters WIP * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md * Update 0000-example-extension.md * Update 0001-digest-algorithms.md * Update README.md * Update 0001-digest-algorithms.md * Update 0000-example-extension.md * Create 0002-N-tuple-tree.md * Update 0002-N-tuple-tree.md * Update 0002-N-tuple-tree.md * Update 0002-N-tuple-tree.md * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md * Update 0000-example-extension.md * Update 0001-digest-algorithms.md * Update 0002-N-tuple-tree.md * Update README.md * Update 0002-N-tuple-tree.md * Update 0002-N-tuple-tree.md * Update 0002-N-tuple-tree.md
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 have some problems with n-tuple extension definition, but I thought it made sense to address those separate from the changes to how extensions are specified.
I think we'll do more work on this but I think the PR makes significant progress and will be good to get up as-is, modify with later PRs as necessary |
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.
This generally looks good. Some minor questions.
Additionally, we may want to add a Travis style validator... specifically to limit the line lengths.
* description: Indicates how many chunks are used for path generation | ||
* type: integer | ||
* range: 0,32 | ||
* default: |
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.
Giving a default here may encourage consistency of approach. For example, a "tuple size" of "2" (hex characters) and a "number of tuples" of "4" provides for four billion options. That could be a reasonable default starting point.
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.
Default is to "pairtree" behaviour but I'm open to change.
* type: integer | ||
* range: 0,32 | ||
* default: | ||
* short object root |
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.
There are obviously other potential options for naming the object root. We should be open to the possibility of community feedback on that point.
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.
Those can be other extensions. This is an extension based on generalising pairtree.
Perhaps it would make sense to split this PR in two? One PR for the update to how extensions are defined and referenced and one for the n-tuple layout extension? |
Going to pick up @pwinckles suggestion and split PR's but leave this here until we've processed all the comments. |
First part is in #8 |
For comment rather than commit.