Problem or motivation
I'm trying to port some things from copies of forks that left no changelogs, and finding each dependency and change from the build errors is getting really awkward.
Proposed solution
What if I were able to point it at a file, and have it recursively iterate through everything to show me which other components it references and which ones have it in their using lists/namespaces (adjustable for how many layers back there are?) I would just put each of those on paper and trace it manually, but SS14Editor only searches file names (excluding contents) and windows search sucks balls.
Ideally, I should be able to point it at a mechanically relevant prototype, sight unseen as to what it might talk to, and have it recursively highlight all the dependencies it uses/needs (and the ones those need, ect) not to produce build errors.
Alternatives considered
I'd do it manually, but this would be way better!
Problem or motivation
I'm trying to port some things from copies of forks that left no changelogs, and finding each dependency and change from the build errors is getting really awkward.
Proposed solution
What if I were able to point it at a file, and have it recursively iterate through everything to show me which other components it references and which ones have it in their using lists/namespaces (adjustable for how many layers back there are?) I would just put each of those on paper and trace it manually, but SS14Editor only searches file names (excluding contents) and windows search sucks balls.
Ideally, I should be able to point it at a mechanically relevant prototype, sight unseen as to what it might talk to, and have it recursively highlight all the dependencies it uses/needs (and the ones those need, ect) not to produce build errors.
Alternatives considered
I'd do it manually, but this would be way better!