get_pack_list: Use a prebuilt list of useful packages

Description Usage Arguments Details Examples

View source: R/pack_list.R

Description

get_pack_list

Usage

1
2
3
get_pack_list(ref_list = "whyles", show_packs = NULL, source_from = NULL,
  cloud_path = NULL, filter_pack = "required", user_name = NULL,
  pw = NULL)

Arguments

from_wd

to specify if this is the directory in edit mode

is

to allow flexibility between projects from the console or within app once launched

Details

For me remembering which packages to load is a hastle so this is a convience function to load libraries based on scope of work

load all the libraries

Examples

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
print to the console the list object to view package hierarchy
get_pack_list(show_packs = TRUE)


load one of your groups
get_pack_list(ref_list = required)

if you prefer nested lists use filter_pack to access the slot
for instance if you have a set of libraries you always use when building
a new package and you wanted your parent node to group together packages that
all relate to a different version such as

packList <- list(dev =
             list(new_packages = c('devtools','rdrop2','roxygen2','plyr','httr'))
             )

get_pack_list(ref_list = 'dev',filter_pack = 'new_packages')

CarlBoneri/autorox documentation built on June 1, 2017, 10:16 p.m.