The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
datanames argument of
get_code(). Use names instead.datanames(). Use names()
instead.datanames(x) <- value. Does nothing,
replace with renaming the objects inside the environment.names() function is introduced replacing
datanames.
join_keys are provided, the names() are
now sorted in topological way (Kahn algorithm), which means
the parent dataset always precedes the child dataset.names() and the connection between child-parent is
set through join_keys and parent exist in
teal_data environment.teal_data environment.teal_data no longer set default names()
based on join_keys names - it uses only data names.get_code no longer adds warning message
about failed verification.col_relabel supports NA to remove labels
(similar to the col_labels<-).get_code causing incorrect lines order of
the returned code.col_labels causing incorrect label names
to be returned when input data contains named label attributes.get_code_dependency bug to detect the usage of
objects in functions on both the left and right-hand sides for code
reproducibility.code_graph.get_code.teal_data() with a possibility to
steer internal methods with ... parameter.join_key to better support primary
keys.JoinKey R6 object was removed in favor of
a list-like object with class name join_keys. Subset
operators and assignments are supported ([,
[[, [<- and [[<-)join_keys function works as a constructor, getter and
setter.teal_data() and cdisc_data() return now
teal_data class object which replaces TealData
class object. teal_data becomes a standard input for the
entire teal framework.TealDataset, TealDatasetConnector or
TealDataConnector classes have been removed.
Delayed-data-loading is no longer supported by teal.data.
So called connectors are now supported by teal package (see
?teal::teal_data_module).join_keys() and join_key() return now
join_keys object which replace JoinKeys
class.teal.code dependency from Imports
to Depends.get_labels function and removed the
supporting function data_label.scda package dependency from examples.col_labels function and removed
formatters dependency.ADQLQC, ADCSSRS, and
ADEQ5D5L as supported data sets.get_cdisc_keys.scda.2022 instead of
scda.2021.TealDataset and
MAETealDataset.reticulate package in
teal.data with Python vignette.teal.Dataset$print method for a less cluttered
output.TealDataset and
MAETealDataset to teal.CDISCTealData class and updated
TealData to account for the removed functionality.JoinKeys
class.cdisc_data and teal_data wrappers
to handle join_keys creation and updating instead of
CDISCTealData and TealData.join_keys methods from
TealDataset, TealDatasetConnector.README content.validate_metadata function.name by archive_name to
comply with the latest version of the
synthetic_cdisc_dataset function.scda with
random.cdisc.dataget_raw_data examples.pkgdown site..Globalenv in Python
code execution.teal.data a package for the data
model used by teal applications.teal)metadata field to TealDataset to
store a named list of metadata items. It is available for
module developers through
FilteredData$get_metadata("<<dataname>>") and
can be pulled or added directly to datasets derived from
TealDatasetConnectors.get_key_duplicates returns a data.frame
instead of a tibble.get_call() function of CallableFunction
now returns call with namespace included.MultiAssayExperiment and
SummarizedExperiment are now suggested packages, not
required. Objects dependent on MultiAssayExperiment are
changed to lazy-load these now suggested packages.TealDataset, for
example some active fields should be replaced by explicit “get”
calls.reticulate is in Suggests, added
requireNamespace call whenever it is needed.dplyr moved from imports to suggests.JoinKeys$mutate method
inside of for-loops.rtables dependency from the package.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.