I think we need to put help for both tb() and [.tb on the same ?tb help file. This help file will be kept short and will be used to redirect to other help files. I think it should document i, j and briefly dots (with links to details on mutate, rename, spread, aggregate features) and just reference other features.
Our args will be referenced by ?.foo, so we'd have ?.by, ?.stack etc.
We could have tidyverse equivalent help files
So we can call ?tb_mutate and we get examples with equivalent dplyr code inside of dontrun{} + additional explanations.
?.fill will go to the documentation of the .fill arg, and ?tb_fill will show equivalent examples.
The good thing is that it'd be part of the help reference, so the main doc can almost read like a vignette.
We'll use aliases so to document ?tb_summarize_at, ?tb_summarize_if, ?tb_summarize_all on the same page. For pivoting functions we'll document tb_pivot_longer, ?tb_melt , tb_gather on the same page too.
I think we need to put help for both
tb()and[.tbon the same?tbhelp file. This help file will be kept short and will be used to redirect to other help files. I think it should document i, j and briefly dots (with links to details on mutate, rename, spread, aggregate features) and just reference other features.Our args will be referenced by
?.foo, so we'd have?.by,?.stacketc.We could have tidyverse equivalent help files
So we can call
?tb_mutateand we get examples with equivalent dplyr code inside ofdontrun{}+ additional explanations.?.fillwill go to the documentation of the.fillarg, and?tb_fillwill show equivalent examples.The good thing is that it'd be part of the help reference, so the main doc can almost read like a vignette.
We'll use aliases so to document
?tb_summarize_at,?tb_summarize_if,?tb_summarize_allon the same page. For pivoting functions we'll documenttb_pivot_longer,?tb_melt,tb_gatheron the same page too.