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
The tidylog package is an amazing supplement to the dplyr and tidyr packages. It allows immediate tracking/debugging of a pipeline by giving high-level information on the results of each step in the pipeline (see below). It's especially useful in tracking joins, which I know was an important part of the error and warning handling made to the join functions in dplyr 1.1.0+.
The silly example below shows what messages tidylog provides about the process.
I always use tidylog by default and I would love to also teach it to my students. But I don't because it works by masking regular tidyverse verbs with a logging version, which eliminates use of auto-complete. In order to implement auto-complete, the maintainer of the tidylog would have to constantly keep up with tidyverse updates even though they are completely separate (elbersb/tidylog#56)
It would be great if this kind of functionality were implemented natively and maintained by the relevant teams so that updates to APIs (e.g. new arguments) would also involve updating the log structure.
The text was updated successfully, but these errors were encountered:
orgadish
changed the title
Add native pipeline/verb logging option similar to tidylog package.
Request: Add native pipeline/verb logging option similar to tidylog package.
Feb 13, 2024
The
tidylog
package is an amazing supplement to thedplyr
andtidyr
packages. It allows immediate tracking/debugging of a pipeline by giving high-level information on the results of each step in the pipeline (see below). It's especially useful in tracking joins, which I know was an important part of the error and warning handling made to the join functions in dplyr 1.1.0+.The silly example below shows what messages
tidylog
provides about the process.I always use
tidylog
by default and I would love to also teach it to my students. But I don't because it works by masking regular tidyverse verbs with a logging version, which eliminates use of auto-complete. In order to implement auto-complete, the maintainer of the tidylog would have to constantly keep up with tidyverse updates even though they are completely separate (elbersb/tidylog#56)It would be great if this kind of functionality were implemented natively and maintained by the relevant teams so that updates to APIs (e.g. new arguments) would also involve updating the log structure.
Created on 2024-02-13 with reprex v2.0.2
The text was updated successfully, but these errors were encountered: