-
Notifications
You must be signed in to change notification settings - Fork 24
previous content from parsnip vignette for predictions #128
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
base: main
Are you sure you want to change the base?
Conversation
|
Is this in relation to tidymodels/parsnip#1293? |
EmilHvitfeldt
left a comment
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 document is so long!!!
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 like the hierarchy of mode > model type > engine that you've used. I would combine Emil's suggestion of allowing the TOC to go one level deeper with putting the mode in h2, the model type in h3 (both visible in the TOC), and reusing the element from the parsnip article of hiding everything related to one engine underneath the <details> tag. That should make it easy to navigate to the relevant example quickly and a bit more obviously than via the TOC on the right-hand side.
Co-authored-by: Emil Hvitfeldt <[email protected]> Co-authored-by: Hannah Frick <[email protected]>
…e. It disables most of the code from running for now to make it easy to render test
|
@hfrick I think that my changes are all done; please re-review when you get a chance. |
Looking for suggestions on reordering/restructuring.
Spark is aspirational right now (there are some
eval: falseoptions currently).The TODO list:
<details>for long model prints (<cough>C5<cough>)