Project diagnostic ?

[moodymudskipper]

This is useful for refactoring so it's in scope I think.

If I get access to a new repo I want to know as many things as possible right away, possibly in some report, maybe that fits in the viewer using tabs :

• Is it a package
• If it's a package does it use .onLoad, .onAttach
• Show folder structure, maybe a collapsable tree, or a static view similar to lobster::ast but showing folders and number of files per extension
• does it use renv, version control ?
• does it use options
• What are all the folders containing R files
• Does it contain data : find csv, xlsx, rds etc and summarise locations
• Does it contain doc: find html, pdf, docx
• Does it contain a shiny app (could have its own diagnostics)
• Does it use some non recommended idioms such as <<-, setwd(), assign() etc
• Does it refer to absolute paths
• Do we have spaces in file names
• What packages does it use (fetching calls to library(), require(), :: etc + NAMESPACE/DESCRIPTION if applicable)
• can we draw a tree of the dependencies through fun calls and source calls ? We could improve flow::flow_view_deps first and use it