-
Notifications
You must be signed in to change notification settings - Fork 50
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
Split Machinery and Tabulation - Dev Guide #614
Conversation
…nto 568_dev_guide_split@main
Signed-off-by: Davide Garolini <[email protected]>
…nto 568_dev_guide_split@main
inst/dev-guide/dg_tabulation.Rmd
Outdated
|
||
## Disclaimer | ||
|
||
Any code or prose which appears in a version of this vignette on the `main` branch of the repository may reflect a specific state of things that can be more or less recent. This guide reflects very important pieces of the split machinery that are unlikely to change. We anyway invite the reader to think always that the current code may have drifted from the following document, and it is always the best practice to read directly the code on `main`. (xxx we should insert it automatically) |
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 we should insert this automatically. @edelarua @ayogasekaram you remember how best to add this from a common source?
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 the way we did this previously (in tern
?) only worked for Roxygen documentation, i.e. creating a doc with the blurb and reusing it with a few words changed in multiple places.
Code Coverage Summary
Diff against main
Results for commit: b364d87 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Signed-off-by: Davide Garolini <[email protected]>
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.
Hi @Melkiades,
The dev guide sections look great! I made a few grammar/wording edits but nothing big and it was very easy to understand. I also applied the styler to the code blocks but didn't actually change any of the code. There's a few sections with "xxx" which I assume you will still want to edit, plus we will need to add some links in (probably better to do in one of the following PRs after publishing to the pkgdown site), but I think it's fine for now especially since we have the disclaimer.
Amazing work as always!! :)
|
||
```{r, eval=FALSE} | ||
# rtables 6.0.2 |
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.
ops... we should get to 1.0.0 at some time :D
Fixes #568
fyi @ayogasekaram. We can meet anytime to exchange opinions and ideas on structure and content