Movatterモバイル変換

envsetup 0.3.0

• paths no are no longer attached to the search path(#80)
• paths objects default to the global environment now,but they can be changed using theenvsetup.path.environmentoption (#80)
• get_path() was added to help you retrieve a path withchanging the storage environment using theenvsetup.path.environment option (#80)
• autos are no longer attached to the search path, andare sourced to global (#81)
• rprofile lets you specify if sourcing of autos shouldoverwrite an object in global if it already exists (#81)
• extensive messaging added to make users aware of autos beingattached and conflicts (#81)
• object metadata storage is added to track what functions weresourced from where, seeenvsetup_environment$object_metadata (#81)
• vignettes updated to divide content into smaller chunks (#82)

envsetup 0.2.1

• set_autos() will now handle NULL hierarchical paths(#66)
• set_autos() will account for using@include to define function dependencies (#70)

envsetup 0.2.0

• library() will no longer actively reset autos, insteadplacing newly attached packages in the correct position that respectsexisting autos (#59)

envsetup 0.1.0

• Minor updates to prepare for initial CRAN release (#55)

envsetup 0.0.1

New Features

• init() added to assist with setting up a project to useenvsetup (#20, #21, #31)
• build_from_config() added to add ability to also useconfig to create your directories (#25)
• validate_config() added to assist with creatingconfiguration files (#23)
• rprofile() will automatically store your configurationfile in a standard location with a standard name, allowinglibrary() to use this to re-assign autos

Breaking Changes

• library() will now respect invisible return instead ofalways returning the list of attached packages (#24)
• set_autos() now expects a different YAML structure forhierarchical filtering based on ENVSETUP_ENVIRON (#28)

Bug Fixes

• read_path() andwrite_path() will workcorrectly now even if the path objects exists in other environments(#36)