NEWS.md
check.errors
attribute in returned logical valuecheck.errors
blueprintr::filter_variable_lineage()
options(blueprintr.warn_empty_blueprints_dirs = TRUE)
.SOURCE("table_name")
and mark_source(obj)
to add variable (and table) lineage to non-blueprint-created tables. Particularly useful for including data fetched from the web into lineageoptions(blueprintr.use_variable_uuids = TRUE)
. Visualize variable lineage with blueprintr::vis_variable_lineage
or inspect specific parts of the graph with an igraph generated with blueprintr::load_variable_lineage
.blueprintr::vis_table_lineage
and inspect specific parts of the graph with blueprintr::load_table_lineage
.blueprintr.use_improved_annotations
. Metadata now always overwrites annotations in the output dataset, but mutate_annotation()
and mutate_annotation_across()
will override the metadata safely. No longer a need to mess with annotate_mutate
!blueprintr.interactive_eval_macros
option to TRUE
to enable.metadata_file_path
based on the directory and name of the affiliated blueprint script. For example, a blueprint defined in “blueprints/ex/test.R” will get its default metadata file location set to “blueprints/ex/test.csv”. Set the blueprintr.use_local_metadata_path
option to TRUE
to enable.bpstep()
and bp_add_step()
for customizationkfa::kfa()
using the kfa_args
parameter in bp_export_kfa_report()
bp_extend()
would clobber the results of bp_add_bpstep()
_final
stage.with_names
parameter to mutate_annotation_across
that, when TRUE
, sends a column and its name as arguments to .fn
..TARGET()
calls.mutate_annotation()
and mutate_annotation_across()
which allows runtime transformation of metadata. Useful for batch transformations before metadata creation.recurse
parameter to load_blueprints()
and tar_blueprints()
to recursively load blueprints from the provided directory
panelcleaner
to import homogenized codings if target data.frame is a mapped_df
bp_include_panelcleaner_meta()
extension to signal blueprintr to add mapped_df
metatar_blueprint()
and tar_blueprints()
create_metadata_file()
to return the metadata file path. To compensate, a new build step *_meta_path
has been added that removes the metadata logic inconsistency. Target topology should be much cleaner and clearer.group
fieldfile
parameter for bp_export_codebook()
to access codebook_file
parameter in blueprintbp_export_codebook()
and bp_label_variables()
that create a pipe-able method of setting blueprint configuration.render_codebook()
(#3)blueprint(..., labelled = TRUE)
. Handy to have when making datasets intended to be used in a STATA or SPSS environment.load_blueprint()
or load_blueprints()
(#10)