Open mbcann01 opened 6 years ago
Random Idea: Click on a node, and check that all needed inputs for the current node are available (i.e., check that data exist in read_ function paths). If not, the app returns a list of data inputs that are needed, file name and line number (e.g. data_01_clean.Rmd, line 28) that reads in the data, and the path where it expects to find them ("users/bradcannell/Desktop/data.csv").
Random idea: Use testthat or assert to check for changes that occurred after upstream modifications to code.
Should we make Pathfinder a Shiny App?
If we think of Pathfinder as an interactive tool for understanding a data analysis project, then Shiny might be a great way to implement that tool.
Put a (txt) description file at the top level of each project that stores metadata about the project that the Shiny App can use?