Closed mattssca closed 1 year ago
Let's have a discussion on how to categorize the different GAMBLR functions best. This relates to how the functions will be organized on the reference page. This is specified in the _pkgdown.yml file.
This is how the functions are currently being grouped:
Functions used to annotate GAMBL data.
This is the bundled data used by GAMBLR.
Functions tailored to setting up a new study or updating an existing cBioPortal instance.
GAMBLR functions fall under the check category.
A collection of functions used to retrieve data of different types.
Functions used to write or read GAMBL data.
Functions used for visualizing GAMBL data.
Functions used for executing statistical and other calculations on incoming GAMBL data.
A collection of functions that fall under the utility category.
Besides updates relating to GAMBLR website, this PR also includes an update to finalize_study
. This update allows for additional sample-level summary fields to be added to the clinical metadata file. The function now internally calls collate_results
and joins with the full metadata. This allows us to pick any columns available in the collated results output (and the standard metadata). If no such columns are specified, the function will run in the same way it did prior to this update.
See function documentation and examples for more info.
This is the updated groups and contents (based on the discussion in Slack) of the reference page;
Functions used to annotate GAMBL data.
This is the bundled data used by GAMBLR.
Functions tailored to setting up a new study or updating an existing cBioPortal instance.
GAMBLR functions that fall under the check category.
A collection of functions used to retrieve data of different types.
Functions used for visualizing GAMBL data.
Functions used for executing statistical and other calculations on incoming GAMBL data.
A collection of functions that fall under the utility category.
Pull Request Checklists
Important: When opening a pull request, keep only the applicable checklist and delete all other sections.
Checklist for all PRs
Required
[ ] I tested the new code for my use case (please provide a reproducible example of how you tested the new functionality)
[ ] I ensured all dplyr functions that commonly conflict with other packages are fully qualified.
This can be checked and addressed by running
check_functions.pl
and responding to the prompts. Test your code after you do this.devtools::document()
) and addedNAMESPACE
and all other modified files in the root directory and underman
.Optional but preferred with PRs
Checklist for New Functions
Required
[ ] I documented my function using ROxygen style.)
[ ] All parameters for the function are described in the documentation and the function has a decriptive title.
Example:
import
statment.Example:
Checklist for changes to existing code
[ ] I added/removed arguments to a function and updated documentation for all changed/new arguments
[ ] I tested the new code for compatability with existing functionality in the Master branch (please provide a reprex of how you tested the original functionality)