.OpenServer
(dot-OpenServer) instead of OpenServer
for the R6 classOpenServerR6
class inherits from .OpenServer
class. We will not use old OpenServer
because collides with openserver()
function.newOpenServer()
that represents .OpenServer$new()
or OpenServerR6$new()
.setOpenServer()
as it does the same as newOpenServer()
.get_all_models_by_ext()
to retrieve all models residing in packagecore.R
in class, functionsutils.R
zzz.R
dataobjects.R
README
DESCRIPTION
.BiocStyle
package that provided nicer css
. It was making installation complicated.common.R
for unit tests functions.test-status.R
README
for RDCOMClient
installationpkgdown
pkgdown
requires building README, install package before building the documentation website._pkgdown.yml
demo
scriptsRDCOMClient
function createCOMReference()
with @keywords internal
OpenServer$new()
R62S3
because they are stored in in a local environment.README
to a unit test, getting this error when using this form of DoCmd
and DoGet
: DoCmd(prosper_server, open_cmd)
.
Here is the output:> library(rOpenserver)
>
> test_check("rOpenserver")
-- 1. Error: README code behaves the same in tests (@test_readme.R#26) --------------------------------------
object 'open_cmd' not found
Backtrace:
1. R62S3:::DoCmd(prosper_server, open_cmd)
4. private$get_app_name(command)
5. base::toupper(string_value)
This form of command using S3 dispatch works in the README but fails in the unit tests. Why? Even adding object
as an argument to the method in the OpenServer
class doesn't help either. Because the package R62S3
conveniently generates the S3 methods for R6 classes but through the environment, which is not available at unit test time.
testthat
from sourceDoCmd
works. It doesn't. Still getting error at the unit test.setOpenServer
that acts as a OpenServer constructor. OpenServer
without using OpensServer$new()
. Attempts unsuccesful witout sacrificing documentation, and renaming main class to .OpenServer
, that is dot OpenServerNEWS.md
file to track changes to the package.openserver
package works fine but didn't have any roxygen2 documentation.Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.