-
Notifications
You must be signed in to change notification settings - Fork 70
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
Updated tutorial to cover new method of building datastores #497
base: main
Are you sure you want to change the base?
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
I don't think this PR addresses #480 yet, but I think we could add that in straightforwardly whilst we're working on the same notebook? |
I don't think we want to change this until we are directing folks to use |
Good question, I don't know - I thought hh5 had already been retired? But yeah, agreed that changing things too early is not ideal. |
@@ -13,7 +13,10 @@ | |||
"\n", |
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.
Do we still need "The old way"?
If "the old way" is not suggested anymore let's drop it?
Reply via ReviewNB
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.
The old method gives people a little more control over the datastore building process, so I think it's worth keeping around. I've reworded things to make that clearer though.
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.
Assuming this - Great! Let's not call it "Old" and "New" then? Can we give a more descriptive name?
comment got into the wrong thread - the changes should be here.
Let me know if you think this clarifies?
@@ -13,7 +13,10 @@ | |||
"\n", |
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 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 like a misformatted code block in a markdown cell, just pushed what should be a fix
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.
Yup, fixed.
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.
Great! Let's not call it "Old" and "New" then? Can we give a more descriptive name?
No description provided.