Antoine Fabri

Hi, have you tried `out = "pdf"` or `out = "html"` ? If it doesn't work out please open a separate issue and provide an example of a problematic function...

@joint-hubs it might be possible, everything that can be done with diagrams to understand code better is in scope for this package. I'd need more details and examples though, can...

See https://github.com/cynkra/dm/issues/1153 for dm/DiagrammeR solution (WIP). We can probably do the something similar. We need to investigate: * Clickable nodes * Clickable words 1st step is to detect click /...

It should be a new function, because `flow_view_deps()` 's scope is several packages in the general case. I think this new function, let's name it `flow_view_uses()` has 2 main args...

Isn't this what my `pkg` arg described above would do ? I can extend it to environments, and also add an `inherits = TRUE` argument. ``` #' @param f A...

horrible fix/hack : trace(flow:::namespace_name.character, quote(x[x == "system.file"]

I had thought about it but didn't find a satisfying solution at the time so skipped it. A few ways to do it : * Use `grep(pattern, getNamespaceExports("pkg"), value =...

I think we can have `pkg_subset(pkg, subset = c("all", "exports", "imports", "reexports", ...), pattern = NULL, predicate = NULL, value = FALSE, prefix = TRUE)` which would return a character...

The opposite view is also interesting, show me everything that led to building a given variable.

Do you want `flow:::flow_data()` ? I used to export it so users could extend the package, but decided against it to limit features to more important features and make the...