It is not yet very robust because it doesn't solve ambiguity in case of colliding names, something flow_view_deps and flow_vars do a little bit better.
It also stops when it encounters a S3 ethos that is only called through its generic, in these cases it should optionally be shown.
In any case all this logic of structuring the package into rectangular data should be done (and done better) in a separate package, that flow should import.
Closes #92
Created on 2022-11-24 with reprex v2.0.2
It is not yet very robust because it doesn't solve ambiguity in case of colliding names, something flow_view_deps and flow_vars do a little bit better. It also stops when it encounters a S3 ethos that is only called through its generic, in these cases it should optionally be shown.
In any case all this logic of structuring the package into rectangular data should be done (and done better) in a separate package, that flow should import.