Reusing R code¶
When you write a lot of R code in a project, or across projects, you will often want to make reusable parts of code.
DSS provides several mechanisms for reusing R code:
- Packaging your code as functions or modules, and making them available in a specific project
- Importing code that has been made available from one project to another
- Packaging your code as functions or modules, and making them available in all projects
- Packaging your code as a reusable plugin, and making it available for coder and non-coder users alike
If you have created libraries in a project A, you can import them in project B. The libraries of project A will be added to the source path of all code running in project B.
- Go to the library editor of project B
- Open the
- Edit the
importLibrariesFromProjectlist and add the project key (which appears in the URL, i.e. not the project display name) to it
- Save the
You need to have “Read project content” permission on A and “write project content” on B.
Although not recommended, if you have shell access to the DSS machine, you can modify the library folder directly in
The source mechanism is practical but does not enforce namespacing. To get namespacing, you need to build a complete R package, compile it, and install it (possibly in the code environment) using
install.packages. This generally requires shell access on the machine running DSS.