You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* basic logging for select, mutate, and transmute
* unit testing for logs
* remove deepdiffs dependency
* adds tests for logs on the rest of the functions
* typo fix
* add mutate numbers to log
* adds join logging, fix cov x
* Fix esedge case for logging with grouped data frames.
* :newsize mode logs correct type
* add detail for row_change and col_change
* add brief docs, bump v, up news
* fixes log when grouped mutate, adds fillmissing, dropmissing log support
* fixed fxn call
* fix join log if stmnt, bump cov attempt w 2tests
* add slice log support
* change slice_min_max to not use`@filter` bc of logging msg dupes
* adds unite, sep, sep_rows
* adds logging for nests
* minor docs edits for settings
* exclude log.jl from code coverage for now
---------
Co-authored-by: Daniel Rizk <[email protected]>
Co-authored-by: Karandeep Singh <[email protected]>
# TidierData.jl comes with two settings that make it easier to understand the transformations that are being applied to a data frame and to troubleshoot errors. These settings are `log` and `code`. The `log` setting outputs information about the data frame after each transformation, including the number of missing values and the number of unique values in each column. The `code` setting outputs the code that is being executed by the TidierData.jl macros. By default, both settings are set to `false`. This page will review the `log` and `code` settings using the movies dataset.
2
+
#
3
+
# We recommend setting the `log` setting to `true` in general, and especially when you are first learning TidierData.jl. This will help you understand how the data frame is being transformed at each step. The `code` setting is useful for debugging errors in TidierData.jl chains.
4
+
5
+
using TidierData
6
+
using RDatasets
7
+
8
+
movies =dataset("ggplot2", "movies");
9
+
10
+
# ## `log`
11
+
# Logging is set to `false` by default but can enabled as follows:
12
+
13
+
TidierData_set("log", true)
14
+
15
+
# When enabled, each macro called will show information about its transformation of the data. Logging can be especially useful to catch silent bugs (those that do not result in an error).
16
+
#
17
+
# When column values are changed, it will report the number new missing values, the percentage of missing values, and the number of unique values.
# Code printing is set to `false` by default. Enabling this setting prints the underlying DataFrames.jl code created by TidierData.jl macros. It can be useful for debugging, especially for users who understand DataFrames.jl syntax, or for filing bug reports.
0 commit comments