Releases: nyuglobalties/blueprintr
Releases · nyuglobalties/blueprintr
blueprintr 0.2.7
blueprintr 0.2.6
blueprintr 0.2.5
- Add capability to embed custom messages to check results, using
check.errors
attribute in returned logical value - Refactor side-effect messages from built-in checks to
check.errors
blueprintr 0.2.4
- Fix for issue where labelling large datasets would take a very long time
blueprintr 0.2.3
- Add ability to filter variable lineage with
blueprintr::filter_variable_lineage()
- Add tooltop for variable node in variable lineage
- Fix issue where grouped nodes in visNetwork would scale, harming legibility
- Convert empty folder warning to option. Enable with
options(blueprintr.warn_empty_blueprints_dirs = TRUE)
blueprintr 0.2.2
- Adds
.SOURCE("table_name")
andmark_source(obj)
to add variable (and table) lineage to non-blueprint-created tables. Particularly useful for including data fetched from the web into lineage - Fixes lineage legends to focus on object type, rather than grouping. In large projects, the table groups would make the legend explode with the number of labels, rendering it useless.
blueprintr 0.2.1
- Implements variable lineage through
options(blueprintr.use_variable_uuids = TRUE)
. Visualize variable lineage withblueprintr::vis_variable_lineage
or inspect specific parts of the graph with an igraph generated withblueprintr::load_variable_lineage
. - Visualize blueprint table lineage with
blueprintr::vis_table_lineage
and inspect specific parts of the graph withblueprintr::load_table_lineage
. - Implements improved annotations through an option
blueprintr.use_improved_annotations
. Metadata now always overwrites annotations in the output dataset, butmutate_annotation()
andmutate_annotation_across()
will override the metadata safely. No longer a need to mess withannotate_mutate
!
blueprintr 0.2.0
- Adds ability to run macro statements in interactive mode. Very useful when debugging pipelines! Set the
blueprintr.interactive_eval_macros
option toTRUE
to enable. - Adds ability to set
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 theblueprintr.use_local_metadata_path
option toTRUE
to enable. - Fixes a bug where targets patterns were being evaluated prematurely
blueprintr 0.1.3
- Fixes an issue where qualified expressions like "package::thing" were not being translated correctly
blueprintr 0.1.2
- Fixes double-sided formulae rendering in blueprints
- Exports
bpstep()
andbp_add_step()
for customization - Allows argument forwarding to
kfa::kfa()
using thekfa_args
parameter inbp_export_kfa_report()